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.

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"

Pushed by npierron@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/031089f91a7c List JS bytecode cache preferences in all.js. r=mrbkap