6.009 stuck 100% CPU when launch

Bugs or Unexpected Behavior
1

Note:
Before bug reporting, please make sure you have tried the latest (alpha) version of BetterTouchTool and that you have already tried to restart your system :-). If you encounter a crash, please attach a crash log from the macOS Console.app's "Crash Reports" section.

Describe the bug
Updated to 6.009 (forgot what last version is, I might have updated CTT in Dec 2025 previously and it was working), Launch and 100% CPU not responding in Activity Monitor. Restart laptop no help.

Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):

Had quite a few config incl Logi, but I disabled Bluetooth to disconnect all of them, still stuck.

Screenshots
If applicable, add screenshots to help explain your problem. (You can just paste or drag them here)

Device information:

  • Type of Mac: Apple M1 Pro
  • macOS version: 26.2 (25C56)
  • BetterTouchTool version: 6.009

Additional information (e.g. crash logs, related issues, etc.):

It’s ok now after I went back to 5.800

What’s also tricky is 6.009 shows up when I update Check for Regular Release…

2

100% cpu usage usually means something is triggering itself endlessly. Sometimes it is also an issue with the experimental Dropox & iCloud sync if you have that enabled.

You can try quitting BTT and running this terminal command to enable safe mode:

defaults write com.hegenberg.BetterTouchTool BTTSafeModeEnabled YES

Afterwards you can launch BTT and check the "Recently Used" section to see whether anything weird is showing up in there.

3

I did BTTSafeModeEnabled in 6009, it still hangs

4

Can you start BTT, then try to create a process sample using this terminal command?

sample BetterTouchTool > ~/Desktop/btt.txt

It will save a btt.txt to your desktop, please post that here

5

btt.txt (225.4 KB)

attached, done with 6.011

6

tried 6020, seems good now.

btw it seems for MX Anywhere 3, Button 6 is now Button 7, assume expected, no big deal, but would be good to mention in release notes.

thanks for looking into this!

7

Do you have a MX Anywhere 3 or MX Anywhere 3S?

Your 100% cpu usage was caused by a weird database corruption. There is some trigger in your BTT database that has itself as parent relation. I'm not sure how that could happen, but I have added a check to prevent issues with that now.

8

Thanks for explanation. My mouse is MX Anywhere 3, the extra buttons are 3/4/7 (in 5.800 they were 3/4/6)