Closed
Bug 1753932
Opened 3 years ago
Closed 3 years ago
Investigate which preference(s) are written late
Categories
(Core :: Preferences: Backend, task)
Core
Preferences: Backend
Tracking
()
RESOLVED
FIXED
99 Branch
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: jstutte, Assigned: jstutte)
References
Details
Attachments
(1 file)
In pref_SetPref
we added a check for late-in-shutdown preference write attempts.
Based on bug 1752308 comment 8 we might want to add better diagnostics in debug builds to see where those late attempts come from. IIUC we want to:
- re-introduce the debug assertion we initially had
- add additional information (JS stack) to the log output
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → jstutte
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•3 years ago
|
||
This patch will most likely cause new intermittents similar to bug 1752308. Thus we can close this one when the patch lands and wait for those to appear.
Pushed by jstutte@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6bc4dbac64bb
Add JS stack dump and debug assertion on late preference writes. r=Gijs
Comment 4•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox99:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 99 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•