Clipboard manager sluggish after update

Since I updated BTT recently, the clipboard manager is sluggish. It's been updated with new features I guess, but it also made it so slow that I Frequently make mistakes during rapid-fire work.

I call it open which is as before, but arrow downs brings a significant delay before the next row is selected. It used to be instant. Anyone else experiencing this? It's really a downgrade, I'd rather remove the new featurs, whichever they are, and have it being fast again.

that is weird. On my machines it got quite a bit faster since there were also some optimizations.

Is it happening with specifics items?

Mostly text really, All I found otherwise is a file link or something further down the list, but that wasn't there earlier today when it was also quite slow. It's a lot of items, that's all I can think of. But it was before the upgrade as well.

It takes time to load up the window at first, then it takes time moving down the list. Scrolling list is jerky and choppy. Quite hard to use it.

can you check whether any process is using a lot (>= 100%) of CPU via Activity Monitor? (I just tried on my other two machines, but the clipboard manager works really smoothly on all of them)

Which version of macOS and BTT are you on?

Nothing strange in activity monitor, I'm <10% cpu use.

I'm on 14.7.2 (23H311) and BTT 5.072.

With the newest update, where you state that some updates were done to the clipboard manager, things got better. It's now resonably fast again with ONE annoying caveat: I call it up with the keyboard shortcut, and it happily pops up quickly, but if I immediately press arrow down in order to select the next-to-last entry, half a second later, BTT pops back up to the first entry in the list. I have to wait until text is populated in the right part of the window before navigating, or my navigation is reset back to first entry once the right pane is populated with data.

See video. It doesn't seem like a lot but it's a lot worse in actual experience. Can this be fixed as well?

I can replicate the issue Tigersoul is reporting.

1 Like

ah yes I can also replicate. Will be fixed with the next alpha

1 Like