Hey again, thought I'd wait with this not to be posted until the weekend because I had a suspicion you were a bit unusually busy, Nir.
Good. Let's get to the point:
This is the most unpleasant issue you can imagine on SlskQt.
You can't PREDICT this beast. It will happen, or will not, it might work up to midnight, then you go to sleep, leave slsk idle, then you wake up in the morning - CPU = 100%. No way to change any menu tabs.
A somewhat ridiculous workaround for that is to quit & restart SlskQt multiple times, and if you're lucky, CPU is back to normal again.
However, it has happened rarely that even after 10 quit/restart cycles, CPU was still 100%.
Currently, I'm trying to always keep a recent (!!) backup of my data file. However, this is not as easy as it sounds since as far as I can see SlskQt does NOT always write to the file when running, but rather not until quitting the app (?? please correct me if this is wrong). Had it a couple times that I restored a .Soulseek file and then there were lots of very old downloads (though finished long time ago) and obsolete settings in there.
Ah, it might be important to say that in CPU = 100% state, Slsk *MUST NOT* be quit with the 'X' on its window. If you do it after all, the process will still remain in the system.
This is why I always 'kill' or 'killall' the process to avoid leaving behind a "SlskQt zombie".
Wonder if anyone but me got the same strange thing on his Linux distro. Probably not. :)