Closed
Bug 1778747
Opened 2 years ago
Closed 2 years ago
Crash when accessing 'print_printer' preference in Content Process with blocklisted preferences.
Categories
(Core :: Preferences: Backend, defect)
Tracking
()
VERIFIED
FIXED
104 Branch
Tracking | Status | |
---|---|---|
firefox104 | --- | verified |
People
(Reporter: djackson, Assigned: tjr)
References
Details
Attachments
(1 file)
I was able to reliably crash the content process when navigating to print-friendly pages. I tested on Gmail and https://esta.cbp.dhs.gov. In both cases, after selecting the Print Preview icon, the page loaded correctly but then when the Printer dialog should have appeared, the content process crashed.
Disabling the experimental preferences resolved the crash:
- fission.enforceBlocklistedPrefsInSubprocesses
- fission.enforceBlocklistedPrefsInSubprocesses.tmp
- fission.omitBlocklistedPrefsInSubprocesses
- fission.omitBlocklistedPrefsInSubprocesses.tmp
Crash Reports:
Reporter | ||
Updated•2 years ago
|
Component: Security → Security: Process Sandboxing
Product: Firefox → Core
Reporter | ||
Updated•2 years ago
|
Blocks: 1708798
Component: Security: Process Sandboxing → Preferences: Backend
Reporter | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → tom
Status: NEW → ASSIGNED
Pushed by tritter@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/709e57b20c53 Allowlist the other, very similar, printer preference tree r=jwatt
Comment 3•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
Updated•2 years ago
|
Flags: qe-verify+
Comment 4•2 years ago
|
||
I was able to reproduce the crash using an old Nightly from 2022-07-08 https://crash-stats.mozilla.org/report/index/096ddc3d-cc2e-427d-b05c-4cb170220804, verified that using latest Firefox 104.0b5 I don't get a crash anymore across platforms (Windows 10 64bit, macOS 11.6 and Ubuntu 18.04).
You need to log in
before you can comment on or make changes to this bug.
Description
•