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 external 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•3 years 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•3 years ago
|
| Assignee | ||
Comment 2•3 years ago
|
||
10 more crashes:
- intl.hyphenation-alias.de-AT-1996
- intl.date_time.pattern_override.date_medium
| Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Comment 5•3 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Comment 6•3 years ago
|
||
Set release status flags based on info from the regressing bug 1811294
| Assignee | ||
Comment 7•3 years ago
|
||
No new crashes, so that's a good sign!
Comment 8•3 years ago
|
||
:tjr can this be resolved for now or do you still need the leave-open?
| Assignee | ||
Comment 9•3 years ago
|
||
I'm still watching the crashes, so I want to keep it open for now to remind me.
Comment 10•3 years 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•3 years 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•3 years 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
Comment 13•3 years ago
|
||
:tjr Is there anything to do here for 111? Marking as fix-optional for now.
| Assignee | ||
Comment 14•3 years 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•3 years ago
|
||
Depends on D171763
Updated•3 years ago
|
Updated•3 years ago
|
Comment 16•3 years ago
|
||
Comment 17•3 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•