Closed Bug 1364118 Opened 3 years ago Closed 3 years ago

Add bytecode cache preferences to all.js

Categories

(Core :: DOM: Core & HTML, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla55
Tracking Status
firefox55 --- fixed

People

(Reporter: nbp, Assigned: nbp)

References

Details

Attachments

(1 file)

No description provided.
In addition to listing the preferences in about:config, I also extracted the
force option, renamed (bytecode_cache.eager) it and moved it into its own
function.
Attachment #8866839 - Flags: review?(mrbkap)
Component: JavaScript Engine → DOM
Comment on attachment 8866839 [details] [diff] [review]
List JS bytecode cache preferences in all.js.

Review of attachment 8866839 [details] [diff] [review]:
-----------------------------------------------------------------

::: modules/libpref/init/all.js
@@ +210,5 @@
>  pref("dom.compartment_per_addon", true);
>  
> +// Whether to enable the JavaScript start-up cache. This causes one of the first
> +// execution to record the bytecode of the JavaScript function used, and save it
> +// to next to the existing cache entry. On the following loads of the same

"and save it in the existing cache entry"
Attachment #8866839 - Flags: review?(mrbkap) → review+
Pushed by npierron@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/031089f91a7c
List JS bytecode cache preferences in all.js. r=mrbkap
https://hg.mozilla.org/mozilla-central/rev/031089f91a7c
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.