-
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
Error: Failed to initialize the compiled Wasm binary with Wizer #138
Comments
When trying to run locally, it is not responding when calling
I added a few debug statements like |
I've transferred this issue into ComponentizeJS, as it's a componentize error. Ideally we'd debug the Wasm stack here to determine the source of the panic in StarlingMonkey, but without debug tracing it's not possible to do that, so this will be very tricky to debug, down to adding a bunch of log statements to StarlingMonkey source itself to see where it's stopping. The better debugging approach for now would be to run a bisection on the JS code running itself - try break the bundle down into the libraries you're trying to run and try running those libraries one by one, until you get the panic. Note that syntax / runtime errors should display as normal JS errors with an error log. I've added #137 to track getting better debug stacks, although this depends on work in Orca. |
I am able to get better debug stack traces by using the debug build.
|
If I then add
|
It runs successfully with this potential fix bytecodealliance/StarlingMonkey#158 . |
Hi, I'm getting a wizer error when trying to use jco. This is a continuation of troubleshooting of bytecodealliance/StarlingMonkey#15 (comment). In
jco/node_modules/@bytecodealliance/componentize-js/src/componentize.js
, I turned on debugging.I pushed the output debugging sources to https://github.com/cataggar/StarlingMonkey15/tree/main/b0c26fbad66e
The text was updated successfully, but these errors were encountered: