Open
Bug 915861
Opened 11 years ago
Updated 2 years ago
[Async Shutdown] Telemetry on slow asynchronous shutdowns
Categories
(Toolkit :: General, defect)
Toolkit
General
Tracking
()
NEW
People
(Reporter: Yoric, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [Async:ready])
Followup to bug 913899.
> ::: toolkit/modules/AsyncShutdown.jsm
> @@ +222,5 @@
> > + let msg = "A phase completion condition is" +
> > + " taking too long to complete." +
> > + " Condition: " + cond.name +
> > + " Phase: " + topic;
> > + warn(msg);
>
> I wish we could get telemetry (or some other kind of feedback) on this, but
> it's likely to happen too late.
Reporter | ||
Updated•11 years ago
|
Blocks: AsyncShutdown
Reporter | ||
Comment 1•11 years ago
|
||
I believe that most clients will add blockers for profileBeforeChange, or ideally, even before this. Such clients can be recorded by Telemetry, since Telemetry can take into account everything up to profile-before-change, inclusive.
I believe that we could use Telemetry to tell us, for each phase up to profileBeforeChange:
1. how many blockers we have;
2. how long we spend spinning the event loop;
3. which (if any) blockers trigger the timeout warning.
Since 3. is more complicated, I believe that we can postpone it to a followup bug.
Updated•11 years ago
|
Severity: normal → minor
Whiteboard: [Async] → [Async:ready]
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•