Closed
Bug 986104
Opened 11 years ago
Closed 11 years ago
Unexplained failures to start XPIProvider
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
FIXED
mozilla31
People
(Reporter: Irving, Assigned: Irving)
References
Details
Attachments
(1 file)
|
7.00 KB,
patch
|
Unfocused
:
review+
|
Details | Diff | Splinter Review |
Telemetry from bug 952543, combined with other AddonManager telemetry, is showing roughly 0.1% of Nightly sessions where AddonManager.startup() runs to completion, but XPIProvider.startup() does not log its timestamps.
There is a preference, "extensions.defaultProviders.enabled", which could be causing this but I'd be surprised if 0.1% of profiles had that set. Aside from that there's very little code that could fail between where we record AMI_startup_begin and XPI_startup_begin *without* logging an exception. I think the next step is to record extensions.defaultProviders.enabled in telemetry and cover the gaps where we could skip XPI_startup_begin without reporting a failure.
|
Assignee | |
Comment 1•11 years ago
|
||
|
||
Updated•11 years ago
|
Attachment #8400344 -
Flags: review?(bmcbride) → review+
|
|
Assignee | |
Updated•11 years ago
|
Keywords: checkin-needed
|
||
Comment 2•11 years ago
|
||
https://hg.mozilla.org/integration/fx-team/rev/bc716fe4c06d
Should this be leave-open?
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → mozilla31
You need to log in
before you can comment on or make changes to this bug.
Description
•