Closed diktomat closed 2 years ago
You’re using the SetApp version right? This occurs with the SetApp library we have to include.
You can reach out to support@glyphfinder.com and I’ll send you a license key for the non-SetApp version. ✌️
I do. I probably don’t want to think about what this library does on top of verifying the license to produce this load… Thank you for the kind offer, I’ll do and see if it indeed behaves better after.
We have the source code and it’s tracking if and how often you use the app (but not how). The idle load appeared with macOS monterey, but I didn’t have time to debug it yet.
Unfortunately, Glyphfinder Helper (Renderer)
still idles at around 10% CPU, even with the non-SetApp version.
Are you sure you removed the SetApp version? You’re the first one, where it didn’t help. 🤔
Did an Uninstall completely
in Setapp, installed from Brew, and it asked me for the licence key. Frequently used in the app was blank again. Looking in Activity monitor, it's all /Applications/Glyphfinder.app
. So I basically can't find any leftovers from Setapp anywhere 🤷🏼♂️
Hm .. Last try: I think brew installs an older version. Can you try downloading it from the website, just to test that? Sorry, for all the trouble.
I verified before installing from Brew, it's exactly the same download link as on the website, with exactly the same version (1.4.1, the Homebrew formula actually has a livecheck
block, which finds the latest version from the website). Nonetheless, I'll replace it downloaded from the website, and report tomorrow if it changed anything :)
Actually forgot that I wanted to switch to non-brew, but remembered this morning. So I checked first and load was down, rechecked several times during the day and it stayed down. Maybe the reboot I had to do yesterday erased last traces of Setapp inside Glyphfinder, but whatever, it works now without crunching my battery, still managed by brew. 🤷🏼♂️
Amazing! Good to hear. We’ll push a fix to SetApp soon.
Glyphfinder constantly uses >10% GPU on my MacBook Pro 2021, while in the background (see below). For just being there, waiting to be called, this is too much, not to speak of the battery impact it probably has. All it has to do is listen for a hotkey or activation of the menu bar item. I don't know if it's even possible to reduce idle load using
a whole fucking browserElectron (Swift is a very nice language, by the way), but it would be a nice thing to try.