-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
WebAssembly instantiation fails on latest nightly #12740
Comments
IIRC it was segfaulting for me a couple weeks ago, too. |
Was it segfault or sigill though? But yeah, I've tried few slightly older nightlies, they had this issue too. |
/cc @nodejs/v8 |
We should try with V8 5.8. |
Can't test myself right now but here is a branch with V8 5.8: https://github.com/targos/node/commits/v8-5.8 |
There is also one with newer V8 here: v8@4f1a48b |
For now, I've tried prebuilt test binary with V8 5.9 from https://nodejs.org/download/test/v8.0.0-test201704119b43f9c487/ (source: nodejs/CTC#99) and that one works correctly. So the fix was somewhere in between. |
I cannot reproduce on Linux. Tried with |
Ok so it was indeed fixed between 5.7.492.69 and 5.8... Is the plan to update to 5.8 soon or better to do |
The plan is to update to 5.8 before we release 8.0.0 so I don't think we need to find the fix. |
I see. Hoped to play with Emscripten-generated WebAssembly, and only nightly Node has up-to-date API for that, but if it will be updated soon, that can wait. |
Should I close this issue or keep as a tracking issue that others can find until V8 is updated? |
This should be fixed by #12784, probably worth leaving this open so you can verify that Node.js works once that lands. |
V8 5.8 landed on |
Confirmed, seems to work. |
Steps to reproduce:
I've tried nightly because currently stable Node.js 7.9.0 exposes slightly outdated WebAssembly version even with
--expose-wasm
.However, while the nightly one provides up-to-date WebAssembly APIs, it looks like the V8 version it's using is still slightly outdated - 5.7.492.69, so, perhaps it's a known issue that was already fixed on V8 side and just needs to be picked up?
LLDB backtrace
The text was updated successfully, but these errors were encountered: