If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[AsyncShutdown] Make dependencies between barriers clearer

NEW
Unassigned

Status

()

Toolkit
Async Tooling
3 years ago
3 years ago

People

(Reporter: Yoric, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

It is common to have a Barrier A blocked by the shutdown of another Barrier B. A timeout in B may cause a crash report to be produced either for A or for B. If the implementor did not take time to add the state of B to the state of A, the crash report is not sufficient to make the difference.

Therefore, we should make it easier for implementors to make sure that the state of A contains the state of B.

A possible API would be to extend addBlocker to accept a Barrier as a blocker.

Comment 1

3 years ago
David, is this bug still something we might want to do? If so, we may consider mentoring a contributor with some previous experience.
Flags: needinfo?(dteller)
This code is safety-critical. I'm willing to mentor, but as an advanced bug.
Flags: needinfo?(dteller)
You need to log in before you can comment on or make changes to this bug.