Closed
Bug 1802525
Opened 2 years ago
Closed 2 years ago
Why does GiveUpBytecodeEncoding call FinishIncrementalEncoding?
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
109 Branch
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: nbp, Assigned: arai)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
FinishIncrementalEncoding was meant as a way to aggregate every pieces of bytecode generated during the start of web pages, to make it a viable output to be stored in a cache.
GiveUpBytecodeEncoding was meant to gracefully handle failures before being able to store any bytecode in the cache. At this stage our goal reclaim the memory.
FinishIncrementalEncoding does not seems to fit the scenario depicted by the context in which GiveUpBytecodeEncoding might be called.
|
Assignee | |
Updated•2 years ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 1•2 years ago
|
||
Pushed by arai_a@mac.com:
https://hg.mozilla.org/integration/autoland/rev/777f345bd0c5
Do not perform serialization in GiveUpBytecodeEncoding. r=nbp
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox109:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 109 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•