When running wasm in a full browser build, it can happen that some configure options are ignored. I believe this happens, but is impossible to observe, in unmodified m-c sources. However, when the attached patch is applied, the problem is obvious. STR: build on x86_64-linux. Start. Ensure that javascript.options.wasm_baselinejit = false javascript.options.wasm_optimizingjit = false (meaning that we request Baseline-only). Load https://beta.unity3d.com/jonas/AngryBots and observe that only Ion compiles are initiated -- 40366 of them. By contrast, loading https://www.funkykarts.rocks/demo.html produces only Baseline compilation, as expected. I hypothesise (guess wildly, without much insight) that this is somehow to do with the fact that AngryBots test case gets a child process in order to do WebGL stuff (or something like that), whilst Funky Karts doesn't.
Bug 1697560 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When running wasm in a full browser build, it can happen that some configure options are ignored. I believe this happens, but is impossible to observe, in unmodified m-c sources. However, when the attached patch is applied, the problem is obvious. STR: build on x86_64-linux. Start. Ensure that ``` javascript.options.wasm_baselinejit = true javascript.options.wasm_optimizingjit = false ``` (meaning that we request Baseline-only). Load https://beta.unity3d.com/jonas/AngryBots and observe that only Ion compiles are initiated -- 40366 of them. By contrast, loading https://www.funkykarts.rocks/demo.html produces only Baseline compilation, as expected. I hypothesise (guess wildly, without much insight) that this is somehow to do with the fact that AngryBots test case gets a child process in order to do WebGL stuff (or something like that), whilst Funky Karts doesn't.
When running wasm in a full browser build, it can happen that some about:config options are ignored. I believe this happens, but is impossible to observe, in unmodified m-c sources. However, when the attached patch is applied, the problem is obvious. STR: build on x86_64-linux. Start. Ensure that ``` javascript.options.wasm_baselinejit = true javascript.options.wasm_optimizingjit = false ``` (meaning that we request Baseline-only). Load https://beta.unity3d.com/jonas/AngryBots and observe that only Ion compiles are initiated -- 40366 of them. By contrast, loading https://www.funkykarts.rocks/demo.html produces only Baseline compilation, as expected. I hypothesise (guess wildly, without much insight) that this is somehow to do with the fact that AngryBots test case gets a child process in order to do WebGL stuff (or something like that), whilst Funky Karts doesn't.