Unexplained failures to start XPIProvider

RESOLVED FIXED in mozilla31

Status

()

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Irving, Assigned: Irving)

Tracking

unspecified
mozilla31
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

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: nobody → irving
Status: NEW → ASSIGNED
Attachment #8400344 - Flags: review?(bmcbride)
Attachment #8400344 - Flags: review?(bmcbride) → review+
Keywords: checkin-needed
https://hg.mozilla.org/integration/fx-team/rev/bc716fe4c06d

Should this be leave-open?
Keywords: checkin-needed
Whiteboard: [fixed-in-fx-team]
https://hg.mozilla.org/mozilla-central/rev/bc716fe4c06d
Status: ASSIGNED → RESOLVED
Last Resolved: 5 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.