Closed
Bug 695584
Opened 13 years ago
Closed 7 years ago
Detect startup crashes caused by incompatible addons
Categories
(Toolkit :: Add-ons Manager, defect)
Toolkit
Add-ons Manager
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: Unfocused, Unassigned)
References
Details
Part of the self-tests for compatible-by-default addons.
Detect startup crashes, figure out if they're related to an addon, mark that addon as incompatible.
Comment 1•13 years ago
|
||
are you thinking this is a service supplied by general crash stats data or adminstrators of that data, or something the client tries to figure out on its own.
We definitely have suspects in the crash data.
reports like https://crash-analysis.mozilla.com/chofmann/20111019/stats-7.0.1-txt help to isolate crashes that 100% of the time happen within 30-60 seconds of start up, and are strongly associated with addons, and addon compat checking.
often the crashes happen before the compatibility checking happens so we get false indidators there. Here is an example from the report above.
win5.1 0.63
win6.0 0.04
win6.1 0.34
less than 30 seconds 100%
addons not checked 0.0000
crash count 331
signature vksaver3.dll.0x2e55
https://bugzilla.mozilla.org/buglist.cgi?bug_id=614966
that bug has some hints about how we might construct a test case to draw out incompatibility that results in crashes.
Comment 2•7 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•