Closed
Bug 1804613
Opened 1 year ago
Closed 1 year ago
Decouple frontend::NameCollectionPool from JSContext
Categories
(Core :: JavaScript Engine, task, P1)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
110 Branch
Tracking | Status | |
---|---|---|
firefox110 | --- | fixed |
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(1 file)
frontend::NameCollectionPool
should be moved to FrontendContext
(see bug 1787528) or per-process singleton
Assignee | ||
Comment 1•1 year ago
|
||
NameCollectionPool can be owned by either JSContext or FrontendContext.
JSContext's owned NameCollectionPool is used whenever JSContext is available,
to reuse the pool, and FrontendContext's owned NameCollectionPool is used
otherwise.
Updated•1 year ago
|
Attachment #9307551 -
Attachment description: WIP: Bug 1804613 - Add FrontendContext::nameCollectionPool_ and add owned mode. r?bthrall! → Bug 1804613 - Add FrontendContext::nameCollectionPool_ and add owned mode. r?bthrall!
Pushed by arai_a@mac.com: https://hg.mozilla.org/integration/autoland/rev/9e3a7494601e Add FrontendContext::nameCollectionPool_ and add owned mode. r=bthrall
Comment 3•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox110:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 110 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•