Nightly Pref Sanitization Crashes
Categories
(Core :: Preferences: Backend, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox110 | --- | unaffected |
firefox111 | --- | wontfix |
firefox112 | --- | fixed |
People
(Reporter: tjr, Assigned: tjr)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(2 files)
This bug tracks the crashes we're seeing in Nightly after rolling out pref sanitization crashes there. We also rolled out sanitization (no crashes) in 111 which will ride out to beta and then release. We may get bug reports for that behavior (because we have some telemetry coming in we don't understand affecting a small number of users.)
Assignee | ||
Comment 1•1 year ago
|
||
As of this comment:
- 2 crashes (1 user) for
network.protocol-handler.expose.magnet
- this is a user-editing-a-pref mistake, these preferences should be bools not strings - 18 crashes (1 user) for
userChrome.searchSelectionShortcut.keycode
- that's a userchrome thing and I let that community know here
Updated•1 year ago
|
Assignee | ||
Comment 2•1 year ago
|
||
10 more crashes:
- intl.hyphenation-alias.de-AT-1996
- intl.date_time.pattern_override.date_medium
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Pushed by tritter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8fbd405d0347 Allowlist two internationalization custom preferences r=mccr8
Comment 5•1 year ago
|
||
bugherder |
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Set release status flags based on info from the regressing bug 1811294
Assignee | ||
Comment 7•1 year ago
|
||
No new crashes, so that's a good sign!
Comment 8•1 year ago
|
||
:tjr can this be resolved for now or do you still need the leave-open?
Assignee | ||
Comment 9•1 year ago
|
||
I'm still watching the crashes, so I want to keep it open for now to remind me.
Comment 10•1 year ago
|
||
The severity field is not set for this bug.
:KrisWright, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 11•1 year ago
|
||
I'll make it S2 because we are tracking this for release. As we get closer to release we can triple check things and close it out.
Assignee | ||
Comment 12•1 year ago
|
||
Okay, new crashes:
- network.protocol-handler.expose.magnet - Seems to be 2 different users, 1 crash each
- xpinstall.enabled - 6 crashes, all seem to be the same user, with one of them occurring after a reinstall. This is supposed to be a bool also
:tjr Is there anything to do here for 111? Marking as fix-optional for now.
Assignee | ||
Comment 14•1 year ago
|
||
Crashes are still very low and telemetry on release shows 24 distinct users affected since Jan 1. We don't know why those most of those events are coming in (e.g. Bug 1808783), but I did see three that were only affecting one person each (or maybe just one person) that we can safely add to the allowlist.
Assignee | ||
Comment 15•1 year ago
|
||
Depends on D171763
Updated•1 year ago
|
Updated•1 year ago
|
Comment 16•1 year ago
|
||
Pushed by tritter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b345170401db Add three more preferences to the allowlist r=freddyb
Comment 17•1 year ago
|
||
bugherder |
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Description
•