WebAssembly programs start with a fixed amount of virtual memory, and can request additional memory at runtime. They are also encouraged to discard unused physical pages. Can long running, badly behaved WebAssembly programs leak memory? Will this eventually cause the WebAssembly program to crash?
2 Answers
Yes, we are investigating just such a case here!
https://github.com/emscripten-core/emscripten/issues/14459
(Any emscripten / em++ experts are welcome to help ♂️)
The leak starts:
It exhausts available wasmMemory:
After this point, all tested calls to the WASM module fail but that does not crash the tab in desktop Chrome, other browsers might behave differently. (The leak happens in all tested browsers.)
Related