Closed
Bug 1625591
Opened 5 years ago
Closed 5 years ago
Consider allocating RuntimeScriptData and passing as part of Stencil
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
INVALID
People
(Reporter: mgaudet, Assigned: mgaudet)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
It's not clear if this is a good fit for the stencil design today, but is worth talking about.
- A side effect of this we should consider is partially initializing the RSD from offthread, filling in the JSAtoms* we can, while punting the rest to main thread (this presupposes we have a RSD filled with ParseAtomIndexes
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee: nobody → mgaudet
Status: NEW → ASSIGNED
Updated•5 years ago
|
Priority: -- → P2
Assignee | ||
Comment 2•5 years ago
|
||
(Removing assignment, until we have a clear decision here)
Status: ASSIGNED → NEW
Updated•5 years ago
|
Attachment #9136462 -
Attachment is obsolete: true
Comment 3•5 years ago
|
||
With Bug 1638470, the RuntimeScriptData
is trivial. Instead, I'm proposing we move it's allocation to the de-duplication process so that we do not allocate if we will immediately throw away. See Bug 1638668.
You need to log in
before you can comment on or make changes to this bug.
Description
•