Closed Bug 1797183 Opened 2 years ago Closed 1 year ago

Use ErrorContext variant of js::ReportOutOfMemory() for JS modules

Categories

(Core :: JavaScript Engine, task, P2)

task

Tracking

()

RESOLVED FIXED
109 Branch
Tracking Status
firefox109 --- fixed

People

(Reporter: bthrall, Assigned: bthrall)

References

Details

Attachments

(1 file)

There are some uses of reportOutOfMemory(JSContext*) when operating on JS Modules that should be using ErrorContext because they can be used in a helper thread.

See here.

Severity: -- → N/A
Priority: -- → P1
Priority: P1 → P2
Assignee: nobody → bthrall
Attachment #9299992 - Attachment description: WIP: Bug 1797183 - Use ErrorContext variant of ReportOutOfMemory() → Bug 1797183 - Use ErrorContext variant of ReportOutOfMemory() r=arai

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:bthrall, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Flags: needinfo?(bthrall)
Flags: needinfo?(arai.unmht)

The current patch depends on changes in bug 1782573.

Depends on: 1782573
Flags: needinfo?(bthrall)
Flags: needinfo?(arai.unmht)
Pushed by bthrall@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ceae3867e161
Use ErrorContext variant of ReportOutOfMemory() r=arai
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: