Closed
Bug 1661930
Opened 5 years ago
Closed 5 years ago
Include TI flag in bytecode cache MIME type
Categories
(Core :: JavaScript Engine, task, P2)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
82 Branch
| Tracking | Status | |
|---|---|---|
| firefox82 | --- | fixed |
People
(Reporter: jandem, Assigned: jandem)
Details
Attachments
(1 file)
Bug 1661426 part 1 added a TI flag to XDR but that was not sufficient: after flipping the Warp browser pref without updating the build, the bytecode cache can get confused and websites don't load correctly.
I have a patch to add a separate XDR build id. We can then use that in both places.
| Assignee | ||
Comment 1•5 years ago
|
||
This lets us include some extra flags in the MIME type that's used by the bytecode
cache. It also simplifies the XDR code a bit.
The approach is similar to Wasm's GetOptimizedEncodingBuildId.
Pushed by jdemooij@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7a2f08a8a0fc
Add GetScriptTranscodingBuildId and use it for both XDR and bytecode cache MIME type. r=nbp,tcampbell
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox82:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•