Closed
Bug 1722803
Opened 3 years ago
Closed 3 years ago
Always initialize TimelineConsumers at startup
Categories
(Core :: DOM: Core & HTML, task)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
92 Branch
| Tracking | Status | |
|---|---|---|
| firefox92 | --- | fixed |
People
(Reporter: tcampbell, Assigned: tcampbell)
References
Details
Attachments
(1 file)
The TimelineConsumers code currently initializes the singleton on first use, but this can race with Workers which can cause failures. The timeline is used pretty early anyways so it is simpler to just always initialize it in a clear place.
(Sorry, I don't know what component this lives in..)
|
Assignee | |
Comment 1•3 years ago
|
||
Instead of initializing on first use - which can race with workers - do the
initialization in nsLayoutStatics::Initialize(). Also make sInShutdown an
Atomic since it is accessed without locks.
Pushed by tcampbell@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a2b4e9af01ab Always initialize TimelineConsumers at startup. r=nika
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox92:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 92 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•