Krusader stays in an infinite loop when you close it. I looked into it a bit, and it appears to rotate in the qt4 main event loop or something (first time I used GDB, and I’m not a KDE programmer, so I can’t be more exact).
It wouldn’t be half that annoying, if it would not mean, that after some normal usage during the day, not knowing of the problem, you have a lot of krusader processes running in the background, slowing everything down.
And most annnoyingly, since they all get stored in the session, they all come up next morning. Which means a flood of Krusader windows. Plus, when you close them all, of course you’re no better off that before you rebooted. Still slow and everything. (Although as a emergency workaround, you can either force kde, to not store krusader in a session, or just not ever close your single krusader window.)
Steps to Reproduce:
1. Run Krusader.
2. Close its window.
3. Watch it run forever, via top or ps.
4. Run another couple of Krusader processes.
5. Close all those windows too.
6. Log out.
7. Log in again.
Lots of Krusader windows pop up.
Krusader should exit properly, not hog any resources anymore, and not come up at next login. Even when not using above session managemend blocking workaround.
Severety: Crashes = critical, according to Bugzilla.
Also, the file manager is the most important piece of software on a computer, except for the kernel. And since there is no other real file manager for KDE (Dolphin is an insult, even to mentally very limited people.), I say, Bugzilla is about right.
Created attachment 253199 [details]
Fixup ebuild (added patch processing only).
Created attachment 253201 [details, diff]
Ebuild which fixes exit problem with qt >= 4.6.3
There is an exit bug in krusader, yes. Got it after updating to qt 4.6.3.
But for me it didnt eat all cpu, just not exists correctly.
Here is a fixup patch + ebuild:
(patch above is not mine -- ported from krusader trunk).
Fixed in krusader-2.3.0_beta1
Yep, fixed here. But I had a little session manager hiccup where it wasn’t saved in the session at all. Works fine now though. Thanks. :)