I'm not sure yet what is going on yet. My crash signature unknown and points to unknown/JIT code. It happens after "Register and trigger a breakpoint from the original source in C". To test functionality of this bug, we don't need step or debug wasm code. Can we reduce test to minimally test availability of the wasm text in this bug without initiating the entire debugging session? I would like to move the enabling of browser_dbg-wasm-sourcemaps.js into different bug. There might be a reason why it was disabled in first place, and I'm thinking we are hitting just it. Disabling of debugging with opened console is a hire priority and we need to test just that.
Bug 1719615 Comment 32 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm not sure yet what is going on yet. My crash signature unknown and points to unknown/JIT code. It happens after "Register and trigger a breakpoint from the original source in C". To test functionality of this bug, we don't need step or debug wasm code. Can we reduce test to minimally test availability of the wasm text in this bug without initiating the entire debugging session? I would like to move the enabling of browser_dbg-wasm-sourcemaps.js into different bug. There might be a reason why it was disabled in first place, and I'm thinking we are hitting just it. Disabling of debugging with opened console is a higher priority and we need to test just that.