Closed
Bug 1598714
Opened 5 years ago
Closed 5 years ago
Defer LazyScript allocation until after Bytecode Emission is done
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mgaudet, Unassigned)
References
Details
+++ This bug was initially created as a clone of Bug #1598713 +++
Today our deferral story for LazyScripts only extends until just before bytecode emission (see publishDeferredItems
). However we want to push that to after Bytecode emission, in order to eventually allow for all allocation to only happen on main thread.
Updated•5 years ago
|
Priority: -- → P2
Comment 1•5 years ago
|
||
This doesn't make sense any more.
Likely we will fold LazyScriptCreationData into FunctionCreationData and then that into ScriptStencil.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•