Enable wasm in safe mode
Categories
(Core :: JavaScript Engine, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox80 | --- | fixed |
People
(Reporter: jorendorff, Assigned: jorendorff)
References
Details
Attachments
(1 file)
In bug 1649117, it was observed that safe mode makes some websites extremely slow. Part of this might be due to wasm being disabled in safe mode.
In comment 12, jorendorff wrote:
"Safe mode" is a bad term for this—I don't believe it was never intended as a "stricter privacy" mode or a "heightened security for when you want to visit evil.com" mode, but rather as a troubleshooting mode, a "less weird stuff going on in my browser" mode.
Wasm is a feature of the Web platform. Turning it off is like turning off
Promiseoronclickevents. Seems like, on net, that's more weird stuff, not less.
In comment 16, luke wrote:
Yes, agreed with Jason's comment; we shouldn't disable wasm with safe mode. If anything, disabling wasm makes more weird stuff happen, working against the goal of safe mode. To minimize magic, I think it'd make sense to disable tiering. Also, I haven't observed wasm-ion to be any less stable than wasm-baseline (perhaps even the opposite), so, given the perf advantage of the latter, I would recommend that safe mode only disables
javascript.options.wasm_baselinejit.
|
Assignee | |
Comment 1•4 years ago
|
||
|
||
Updated•4 years ago
|
|
||
Updated•4 years ago
|
Pushed by jorendorff@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cc9fae64b426 Enable wasm in safe mode. r=luke
|
||
Comment 3•4 years ago
|
||
| bugherder | ||
Description
•