-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wasm engine panic for ProtectedData #176
Comments
Steps to reproduce:
This is using local copies of jco and ComponentizeJS. It takes about 40 seconds with the typescript compiler reading all those files. |
ComponentizeJS doesn't support debug builds at all - this is due to the nature of the splicing code in https://github.com/bytecodealliance/ComponentizeJS/blob/main/crates/spidermonkey-embedding-splicer/src/splice.rs. Supporting debug builds would be a very worthwhile feature, but involves changing the code injections to handle JS operations at https://github.com/bytecodealliance/ComponentizeJS/blob/main/embedding/embedding.cpp#L89. The error you are seeing is most likely due to this code being incorrect. |
Using the release build of ComponentizeJS, we are back to needing debug traces: The wasm backtrace is:
|
I'm still trying to wrap typescript compiler in a component, but I'm currently stuck on a wasm engine panic. I'm using a local debug build in order to get a wasm backtrace bytecodealliance/jco#537 (comment). I'm having a hard time deciphering the backtrace. The full output is attached. I'll attach steps to reproduce soon.
The text was updated successfully, but these errors were encountered: