Closed
Bug 1783951
Opened 3 years ago
Closed 3 years ago
Use ErrorContext variant of js::ReportOutOfMemory() when encoding/decoding Stencils
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 1786117
People
(Reporter: bthrall, Assigned: bthrall)
References
Details
Attachments
(2 obsolete files)
Stencil encoding and decoding errors should be reported when the encoding/decoding happens off-thread (so script execution can be stopped), and ScriptLoader
uses both main-thread and off-thread encoding/decoding, depending on whether the bytecode is present.
Therefore, we will need encoding/decoding to become JSContext-free so we can create an API for externally-managed threads to use.
Assignee | ||
Updated•3 years ago
|
Severity: -- → N/A
Priority: -- → P2
Assignee | ||
Updated•3 years ago
|
Assignee: nobody → bthrall
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
So we can pass it to ReportOutOfMemory() in XDRBuffer<XDR_ENCODE>.
Depends on D155714
Assignee | ||
Comment 4•3 years ago
|
||
The patch for 1786117 landed first.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Attachment #9291783 -
Attachment is obsolete: true
Updated•10 months ago
|
Attachment #9291784 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•