You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As seen in #416, unexpected WASM crashes throw an ExitStatus instance without any stack trace attached. This makes debugging and reporting very difficult. Emscripten does it on purpose to prevent memory leaks during shutdown, but we want to kill the entire process on failure so memory leaks are not a big issue.
This is the change we need to ensure in php.js – it could be by patching the file or re-assigning the ExitStatus value in the Playground JS library for Emscripten:
classExitStatusextendsError{constructor(status){super(status);this.name="ExitStatus";this.message="Program terminated with exit("+status+")";this.status=status;}}
As seen in #416, unexpected WASM crashes throw an
ExitStatus
instance without any stack trace attached. This makes debugging and reporting very difficult. Emscripten does it on purpose to prevent memory leaks during shutdown, but we want to kill the entire process on failure so memory leaks are not a big issue.This is the change we need to ensure in
php.js
– it could be by patching the file or re-assigning theExitStatus
value in the Playground JS library for Emscripten:Kudos to @wojtekn for identifying the problem
The text was updated successfully, but these errors were encountered: