Bug 169968 - Konqueror doesn't terminate when you close its window.
Summary: Konqueror doesn't terminate when you close its window.
Status: RESOLVED DUPLICATE of bug 167826
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.1.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-28 09:50 UTC by Cláudio da Silveira Pinheiro
Modified: 2008-08-28 11:15 UTC (History)
0 users

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 Cláudio da Silveira Pinheiro 2008-08-28 09:50:58 UTC
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    Ubuntu Packages

Running krunner to check processes' behavior, I saw that when you close a konqueror window its process is not killed, and stays wasting resources. The process is not idle waiting to be reused, as if you open another konqueror window it will create another process without touching the hidden/dormant ones. Those hidden/dormant processes react to SIGTERM, but I'm not sure they close the corresponding kio_http processes.
Depending on usage pattern and available RAM, memory can be quickly exausted by those processes, requiring manual intervention (killing processes, restarting session).
The ancient (and closed as fixed) bug 12309 reports a similar problem in the 1.9.x era konqueror, and as the new konq is a completely different beast I opened a new bug instead of repoening the old one.
Comment 1 Bram Schoenmakers 2008-08-28 09:54:11 UTC
What do your settings say? To check, go to Settings->Configure Konqueror->Performance .
Comment 2 Cláudio da Silveira Pinheiro 2008-08-28 10:54:18 UTC
Minimize memory use: Never
Preloading: Maximum number of preloaded instances: 1, and both checkboxes unchecked.
Comment 3 Bram Schoenmakers 2008-08-28 11:15:59 UTC

*** This bug has been marked as a duplicate of bug 167826 ***