Closed Bug 270543 Opened 20 years ago Closed 20 years ago

Plugin crash causes browser to crash

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 156493

People

(Reporter: theant, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040920
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040920

Anytime any plugin crashes, the whole browser crashes.  It's like this in
Mozilla and in Firefox, and has been for as long as I can remember.  Plugins
should be forked to an entirely separate process, or something along those
lines, so that this does not happen.  It's ridiculous to lose 15 open tabs every
time you happen upon a page that loads a plugin.  There are always going to be
buggy plugins out there -- in my experience, plugins (gxine, mplayer,
realplayer, etc) are buggy more often than not -- and these buggy plugins make
Mozilla/Firefox look like a piece of junk, because to the end-user, "it
crashed."  It doesn't matter who started it.


Reproducible: Always
Steps to Reproduce:
1. Visit a page that loads a buggy plugin (like the red speaker icon on that m-w
page).
2. Watch the whole browser go down in flames.

Actual Results:  
I got mad and yelled.

Expected Results:  
Gracefully print the message: "I'm sorry, there was a problem running that plugin."

*** This bug has been marked as a duplicate of 156493 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Please search before filing new bugs.
see Bug 156493 for sep. process and Bug 230017 for sep. thread
I did.  I searched for "plugin crash" without quotes, it found 25 results, and
none of the subjects matched my problem.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.