Closed Bug 53945 Opened 25 years ago Closed 23 years ago

why isn't browser, mail, composer etc, separate processes?

Categories

(SeaMonkey :: General, defect, P3)

Product:
SeaMonkey
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 115903

People

(Reporter: andre.jonsson, Assigned: asa)

Details

Why should I need to load the mail handler if I'm browsing the web? And when (not if) the browser crashes, the mail goes with it! Same goes ofcourse for the composer, which hardly everyone uses...
I'm marking this as invalid, just because. Seperate processes for each component would not stop the whole thing from crashing unless they were actually called as different programs, which seems like a waste. The idea here is to get the whole thing as stable as possible.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
verified. netscape was also like that. this reduces bloat, as all components are based on one engine (the mozilla engine)
Status: RESOLVED → VERIFIED
The consequence of it being a single process(program) would be to run mail using some other application, until it is stable, and as it seems now, it will probably take a while :-(
Reopening to mark as a dup of bug 115903.
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 115903 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago → 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.