63004 - [rfe] ie parity - Browse as New Process

Status: RESOLVED WONTFIX

(SeaMonkey :: UI Design, enhancement, P3)

Description

[Cesar Eduardo Barros]

To prevent crashage from one page spilling on other pages (or other unrelated
windows, like chatzilla), it would be useful to make each window its own process
(except modal dialogs). Of course it would have to be an option, since it would
use lots of memory.

(this was from the nutty-idea-of-the-week dept. Feel free to mark Future (aka
Never).)

Comment 1

[Asa Dotzler [:asa]]

pretty sure this has been suggeted in several other bug reports.

Comment 2

[timeless]

dupe. squish. threads not processes. squish.

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

Comment 3

[Cesar Eduardo Barros]

No, not dupe.

Bug 61942 wants multiple threads to improve performance.

This bug wants multiple independent processes (not threads) to avoid a bug in
one window from closing everything due to a SIGSEGV. Threads still share a
common address space, which means a bug can easily spill into the rest of the
program.

Comment 4

[timeless]

Assuming that bug 61942 is fixed then the problem that the reporter really 
wants addressed will be solved. Well, in most cases, on well designed 
platforms. eg BeOS, where it's possible to crash threads in many windows while 
still have many working windows.

Marking: arch, helpwanted, future.

Reasoning: Mozilla does not support running more than once see blocker 
[wontfix] bug 40109.

Architecture prohibits us from even considering this.  Until mozilla is capable 
of running in a readonly environment we can't even consider implementing this 
feature because we will clobber ourselves w/ changes to history or localstore 
or mail or preferences.  Result: VERY BAD THINGS (TM).

Sending this to XPApps.  Asking Vishy (Don's replacement) and new ownerof the 
blocker to QA this bug, if you agree that you have no intention of fixing this 
bug please verify wontfix.

Anyone who wishes to fix this bug should feel free to reopen it and reassign it 
to themselves. However, this bug should not be worked on until after all 
blockers are fixed.

Other bugs that would need to be filed and resolved before this bug can be 
opened are support for a mozilla --readonly --nolocking to prevent a new 
instance of mozilla from ever locking files for reading and to prevent mozilla 
from opening files for writing.

If we instead use a different implementation where we have a mozilla instance 
that arbitrates all file/network access then if any problems ever happen there, 
we're toast.

IE has a major advantage in that it can ask the os to do network and cache 
accesses so that it doesn't matter how many instances it has (i verified that 
IE can run multiple times by running four separate instances and asking task 
manager to kill each one individually).

Comment 5

[timeless]

'[e-mail]' will not fix this. Please read previous comments and fix 
all blockers and described blockers before reopening or reassigning.

QA: please verify this resolution.

Comment 6

[R.K.Aa.]

*** Bug 190400 has been marked as a duplicate of this bug. ***

Comment 7

[Nickolay_Ponomarev]

*** Bug 81843 has been marked as a duplicate of this bug. ***