Bug 172037 - Applications don't quit but linger around in mem
Summary: Applications don't quit but linger around in mem
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-02 14:48 UTC by Hannes H
Modified: 2008-12-11 19:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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)