WebAssembly debugging fails with "Process Crashed"

Hi Team,

Please find attached project where we created A Webassembly module and trying to debug same.

Editor : Water
Water version :
Chrome Version : 89.0.4389.114
Added breakpoint on line 12 (var el := Browser.GetElementById(‘helloWorld’); ) of attached project.

Below is the Call stack
~> Process CompleteNewProject started.
~> Server running at WebAssembly file CompleteNewProject.wasm has been loaded. The magic happens here.
~> Process Crashed
~> Process CompleteNewProject terminated with exit code 0. Ran for 3.473

CompleteNewProject.zip (1.2 MB)


I’m afraid this is a bug in the debugging support in the latest Chrome/Chromium versions. It affects, as far as I know, Chrome, Brave and Edge. We have reported this to the Google Chrome team. Until this gets fixed, the oily option os to revert to an older Chrome version (if feasible) or to use the new “Run without debugging” option we enabled for WebAssembly in Fire/Water with build 2615, last week.

my apologies for the inconvenience.


Thank you for quick response.
We will wait for the fix.

1 Like