Bug 172037

Summary: Applications don't quit but linger around in mem
Product: [I don't know] kde Reporter: Hannes H <bugzilla>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: echidnaman
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: FreeBSD Ports   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Hannes H 2008-10-02 14:48:46 UTC
Version:            (using KDE 4.1.1)
OS:                FreeBSD
Installed from:    FreeBSD Ports

Most KDE-Apps don't actually quit, when I close them. Applications that support multiple instances therefor accumulate many instances over time.
E.g.: I have one Konqueror-session open, ps tells me there are about ten. If i keep opening and closing kate-sessions more and more kate-process gather.
KMail and kopete won't quit properly either, but they only respwan their one instance so it doesnt matter much with those.

When quitting KDE, most of these (konq and kate-)zombie-sessions die with SIGSEGV, sometimes also SIGABRT. However the next time I start KDE it actually creates many konqueror instances (which are only visible through ps). Strange enough kate actually opens a empty session for every kate-session I had open before reboot.

Right now i just killall konqueror and killall kate before logout or after login, but it sure seems something is really bugged somewhere...

Or is this whole thing done on purpose to reduce application-startup-time or sth. like that?

Thanks for your help!
Comment 1 Jonathan Thomas 2008-12-11 19:18:31 UTC
This was fixed in KDE 4.1.2, if memory serves. (No clue where the bug report went, though)