Closed
Bug 1883869
Opened 1 year ago
Closed 1 year ago
Make ContentProcessMessageManager::LoadScript become fallible
Categories
(Core :: DOM: Content Processes, task)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
126 Branch
Tracking | Status | |
---|---|---|
firefox126 | --- | fixed |
People
(Reporter: jstutte, Assigned: aiunusov)
References
Details
Attachments
(1 file)
From bug 1882423 comment 1:
So, looking at the stack here I actually think this is an implementation error in ContentProcessMessageManager::LoadScript.
The problem is that this function calls GetOrCreateWrapper, which is a fallible operation, but never actually checks to see if the wrapper allocation succeeded. If wrapper allocation fails here, then the next point where we dereference the pointer is the stack highlighted here.
Reporter | ||
Comment 1•1 year ago
|
||
Would you mind taking this? At a first glance it looks straightforward enough to just do it right.
Flags: needinfo?(aiunusov)
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Attachment #9391227 -
Attachment description: WIP: Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible → Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible
Updated•1 year ago
|
Assignee: nobody → aiunusov
Status: NEW → ASSIGNED
Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(aiunusov)
Updated•1 year ago
|
Attachment #9391227 -
Attachment description: Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible → WIP: Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible
Updated•1 year ago
|
Attachment #9391227 -
Attachment description: WIP: Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible → Bug 1883869 - Make ContentProcessMessageManager::LoadScript become fallible
Pushed by aiunusov@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/030183df6dc9
Make ContentProcessMessageManager::LoadScript become fallible r=smaug
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox126:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 126 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•