Bug 1846122 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Xi Ruoyao from comment #0)
> Even if JIT is disabled via `setDisableIon`, `setWasmIon(false)`, and `setAsmJS(false)`, createJitRuntime is still called by InitSelfHostedCode.  So if W/X mapping is disabled, InitSelfHostedCode will crash.

This doesn't disable all the JITs. You should call `JS::DisableJitBackend()` before creating the first context/runtime and that should prevent the engine from reserving JIT memory.
Revision 1 by
on 
(In reply to Xi Ruoyao from comment #0)
> Even if JIT is disabled via `setDisableIon`, `setWasmIon(false)`, and `setAsmJS(false)`, createJitRuntime is still called by InitSelfHostedCode.  So if W/X mapping is disabled, InitSelfHostedCode will crash.

This doesn't disable all the JITs. You should call `JS::DisableJitBackend()` before creating the first context/runtime (and before `JS_Init*`) and that should prevent the engine from reserving JIT memory.

Back to Bug 1846122 Comment 2