Bug 382741

Summary:	Removal of "Minimise Memory Usage" option makes Konqueror more fragile, please reconsider
Product:	[Applications] konqueror	Reporter:	Jonathan Marten <jjm>
Component:	general	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	stefano.crocco
Priority:	NOR
Version First Reported In:	Git
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonathan Marten 2017-07-26 08:10:02 UTC

In KDE4 and in KF5 until recently, Konqueror had the "Performance - Minimise Memory Usage" option.  Unless this was set to "Always" (with the caution "Use with care"), Konqueror would open new windows in a separate process if it considered it to be appropriate.

Now, with the removal of this option, all Konqueror windows appear to share the same process (i.e. it was as if the former option was set to "Always").  This would not be a problem if everything always worked perfectly, but the trouble is that a single crash (or a hung or runaway process needing to be killed) anywhere - which may not be the fault of Konqueror, but possibly in one of the HTML parts or any other viewer part - will destroy all of the user's Konqueror windows regardless of what they are showing.  And sometimes I have tens of them open...

Please consider reinstating this option, possibly with the default being "Always" if it is felt that this is the most appropriate setting now.

Comment 1 Justin Zobel 2022-11-06 09:24:48 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 2 Jonathan Marten 2022-11-07 16:00:11 UTC

Still an issue with current Konqueror.

Comment 3 Stefano Crocco 2022-11-07 17:15:30 UTC

(In reply to Jonathan Marten from comment #2)
> Still an issue with current Konqueror.

The problem is that we had to switch to a new web engine, QtWebEngine, since the old QtWebKit engine wasn't developed anymore, and the new engine assumes that only one process exists at any time. I don't know whether there's a way to work around this limitation, but doubt it.