Closed
Bug 1915988
Opened 3 months ago
Closed 3 months ago
Fail fast in ContentProcess::Init()
Categories
(Core :: DOM: Content Processes, enhancement)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
131 Branch
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
(Blocks 2 open bugs)
Details
Attachments
(2 files)
If ContentProcess::Init() fails, then we destroy ContentChild and crash. If we crash immediately, then we'll get more specific information about what might be going wrong. The goal is to get more information about what is going wrong in bug 1915788. There's decent volume of that crash on Nightly.
This does not help with NS_InitXPCOM which is its own pile of checks that can fail, but knowing that is failing would at least help a little.
Assignee | ||
Comment 1•3 months ago
|
||
Updated•3 months ago
|
Attachment #9421877 -
Attachment description: Bug 1915988 - Make ContentProcess::Init crash instead of failing. → Bug 1915988, part 1 - Make ContentProcess::Init crash instead of failing.
Assignee | ||
Comment 2•3 months ago
|
||
Updated•3 months ago
|
Attachment #9421882 -
Attachment description: Bug 1915988, part 2 - Make ContentProcess's NS_InitXPCOM infallible. → Bug 1915988, part 2 - Make non-main process NS_InitXPCOM infallible.
Assignee | ||
Comment 3•3 months ago
|
||
Pushed by amccreight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b604929fbaee
part 1 - Make ContentProcess::Init crash instead of failing. r=nika
https://hg.mozilla.org/integration/autoland/rev/107cb232c4f7
part 2 - Make non-main process NS_InitXPCOM infallible. r=nika
Pushed by sstanca@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/4f7a933d8072
part 1 - Make ContentProcess::Init crash instead of failing. r=nika
https://hg.mozilla.org/mozilla-central/rev/21525ab3e367
part 2 - Make non-main process NS_InitXPCOM infallible. r=nika
Comment 6•3 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4f7a933d8072
https://hg.mozilla.org/mozilla-central/rev/21525ab3e367
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox131:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 131 Branch
Comment 7•3 months ago
|
||
bugherder |
You need to log in
before you can comment on or make changes to this bug.
Description
•