Closed
Bug 408721
Opened 17 years ago
Closed 15 years ago
Feature request: Show which plugin causes crash (like MSIE does)
Categories
(Toolkit :: Crash Reporting, enhancement)
Toolkit
Crash Reporting
Tracking
()
RESOLVED
DUPLICATE
of bug 538910
People
(Reporter: mnemo, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: ue)
Attachments
(1 file)
(deleted),
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
So, xmas is coming up fast; here is something from the wish list.
I've noticed that like 9 times out of 10 when firefox.exe crashes, the real cause is actually a third party plugin (a VLC video widget crashing, and thus bringing down all my firefox window etc).
I've noticed that MSIE is actually better than Firefox in this particular area. When MSIE crashes due to a third-party plug-in it will actually tell me which plugin caused the crash (see the attached screenshot). It can't be that hard to add this feature to Firefox as well, no? Maybe some stack tracing breakpad ninja out there knows a way to implement this? Would help to set the record straight on Firefox core vs plugins stability.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
Comment 2•17 years ago
|
||
valid request, breakpad seems to be the best component for this.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: General → Breakpad Integration
Ever confirmed: true
Product: Firefox → Toolkit
QA Contact: general → breakpad.integration
Comment 3•17 years ago
|
||
It would be nice if we could actually get this at some point. Too many people get crashes and blame it on Firefox when it's due to some bogus plugin they didn't need... or flash.
wanted1.9.0.x?
Comment 4•17 years ago
|
||
Not gonna happen on the stable branch.
Flags: wanted1.9.0.x? → wanted1.9.0.x-
Comment 5•17 years ago
|
||
FF3.1 a possibility?
wanted1.9.1?
Flags: wanted1.9.1?
Version: unspecified → Trunk
Comment 7•16 years ago
|
||
I wrote an extension to do this.
https://addons.mozilla.org/en-US/firefox/addon/11217
It's a new and a little rough around the edges, but it works. ;)
Great work Dave! It's really nice to see some traction on this.
Comment 9•16 years ago
|
||
Oh, we lost him!
Where is a new location?
Comment 10•16 years ago
|
||
(In reply to comment #9)
> Oh, we lost him!
> Where is a new location?
Lost the who/what, now? If you mean the link in comment 7, you may want to log in there first. The page is new and the AMO cache takes a bit of time to sync up everywhere. Logging in fixes it for me, and it'll probably show normally by tomorrow.
Comment 11•16 years ago
|
||
See also bug 336872.
Comment 12•15 years ago
|
||
Dave: ever looked at turning this add-on into a patch? Or bug 336872 comment 3, which I apparently wrote at some point?
Comment 13•15 years ago
|
||
(In reply to comment #12)
> Dave: ever looked at turning this add-on into a patch? Or bug 336872 comment 3,
> which I apparently wrote at some point?
I have a few things on my todo list before I'd consider it ready for official inclusion, but yes, that might be a good thing to do at some point. A few parts of it would probably have to be dropped, though. For starters, on startup I explicitly yell at any users with Flash 9 installed. (though, if bug 436348 ever actually gets done I won't need to do that)
Comment 15•15 years ago
|
||
With the miracle that is out-of-process plugins (OOPP) coming, plugins will no longer be able to take down the entire program. Instead, it will simply notify the user that the plugin in question has died and give them the option to refresh the tab and plugin instance. Duping to tracking bug for plugin crash UI.
You need to log in
before you can comment on or make changes to this bug.
Description
•