Closed
Bug 1364118
Opened 8 years ago
Closed 8 years ago
Add bytecode cache preferences to all.js
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: nbp, Assigned: nbp)
References
Details
Attachments
(1 file)
7.53 KB,
patch
|
mrbkap
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•8 years ago
|
||
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)
Assignee | ||
Updated•8 years ago
|
Component: JavaScript Engine → DOM
Comment 2•8 years ago
|
||
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
Comment 4•8 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•