Thanks, that's helpful. Setting `allowUnobservedAsmJS` only when the debugger is open would be a good compromise IMO, no further UI should be required. We have a job to do on our side with reducing the volume of debug data, but having it generated only when debugging is plausibly going to happen would help considerably with the current papercut. We probably should also consider (a little later) whether there's a difference between asm.js and wasm as to which policies are most appropriate. That said, I expect asm.js code also does not need to be pessimized when the console is open, only when debugging. And asm.js is dying, we're just waiting for the right excuse to rip out the dedicated asm.js jit.
Bug 1654590 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks, that's helpful. Setting `allowUnobservedAsmJS` only when the debugger is open would be a good compromise IMO, no further UI should be required. We have a job to do on our side with reducing the volume of debug data, but having it generated only when debugging is plausibly going to happen would help considerably with the current papercut. We probably should also consider (a little later) whether there's a difference between asm.js and wasm as to which policies are most appropriate; for the moment, we have allowed the asm.js settings to be applied to wasm code too. That said, I expect asm.js code also does not need to be pessimized when the console is open, only when debugging. (And asm.js is dying, we're just waiting for the right excuse to rip out the dedicated asm.js jit.)