Bug 205552 - Make each konqueror window use a separate process
Summary: Make each konqueror window use a separate process
Status: REPORTED
Alias: None
Product: konqueror
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.3.0
Platform: Gentoo Packages Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-29 05:50 UTC by Jonathan M Davis
Modified: 2016-01-26 03:51 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan M Davis 2009-08-29 05:50:15 UTC
Version:            (using KDE 4.3.0)
Installed from:    Gentoo Packages

Okay, here's the problem. When a particular window in konqueror crashes, it typically takes a bunch of other windows with it. I assume that all the windows in question are part of the same process and that's why they all go. Any konqueror windows that don't crash are presumably in separate processes. In addition, there's no way to control when a particular konqueror window is in its own process or which other konqueror windows it shares a process with. The set of windows which share a process doesn't even seem to stay the same each time that the computer is restarted.

Ideally, when a konqueror window crashes, it wouldn't take any other windows down with it. For that matter, ideally whichever tab caused the problem would be the only one to go, but that's probably asking for too much. It seems to me that by simply putting each konqueror window in its own process, it will make it so that when one crashes, it's the only one that crashes. Maybe it would be too resource-intensive to make each konqueror window be its own process, but if it's at all reasonable to do so, I'd _really_ like it to be that way. And if it's an issue, maybe it can be an option in the preferences as to whether each konqueror window gets its own process or not, allowing people to choose the safety of separate processes or the better performance of fewer processes. Though for all I know, putting them in separate processes will allow for better multitasking and actually improve performance.

In any case, I'd really like it if each konqueror window could be made to run in its own process in order to make it so that when one of them crashes, only the window that crashes actually crashes.
Comment 1 David Faure 2016-01-24 14:14:19 UTC
This should already be the case, at least with webbrowsing windows (not filemanagement windows). Unless you use "New Window" of course. But any window opened externally (by clicking a link in kmail, typing a url in krunner etc. etc.) leads to a different konqueror process, for exactly the reason you describe.
Comment 2 Jonathan M Davis 2016-01-26 03:51:52 UTC
Yes, if you open a new window externally, then you get a new process, but you don't if you use "New Window" within Konqueror, and when KDE first starts up and reopens all of the Konqueror windows that were open when you logged out, I'm not sure that all of those are separate either. The current behavior is inconsistent, and I'd very much like it if every Konqueror window were in its own process. It would be more consistent and more resilient. It's not as big an issue as it once was, since KDE and  Konqueror are more stable than they were in the early days of KDE 4, but it would still be a definite improvement IMHO.