-
Notifications
You must be signed in to change notification settings - Fork 409
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-opt exits with signal 6 #782
Comments
I have experienced the same error signal, but locally on linux ( I suspect this to be related to cargo workspaces, as my setup use this feature as well (orchestrated by Edit: |
I just ran into the same problem. Turns out all I needed to do was install wasm-opt using |
We are experiencing the same issue for at least 3 days on both Ubuntu and CircleCI with Rust Docker image 😞 |
really sorry that folks are running into this- i'll look into it today! if you want- you can pin wasm-pack at 0.8.1 by using the npm installer. alternatively, you can disable wasm-opt temporarily by setting |
I can reproduce this and #781 in
Running the same command manually without the the |
I just changed my installation command in CI to |
I'm also encountering this on my Ubuntu 19.10 machine. The segmentation fault happens every time using the Version Numbers and Environment$ rustc --version --verbose
rustc 1.42.0-nightly (cd1ef390e 2020-01-31)
binary: rustc
commit-hash: cd1ef390e731ed77b90b11b1f77e2c5ca641b261
commit-date: 2020-01-31
host: x86_64-unknown-linux-gnu
release: 1.42.0-nightly
LLVM version: 9.0
$ cargo --version --verbose
cargo 1.42.0-nightly (9d32b7b01 2020-01-26)
release: 1.42.0
commit-hash: 9d32b7b01409024b165545c568b1525d86e2b7cb
commit-date: 2020-01-26
$ wasm-pack --version
wasm-pack 0.9.0 It looks like I tried getting a backtrace using I also tried compiling Installing from source$ cd /tmp
$ git clone git@github.com:WebAssembly/binaryen.git
$ git rev-parse HEAD
33f92aa06fe5de7bcf9f6b7fe2e74ba5e8e1e782
$ mkdir build && cd build
$ cmake -G Ninja -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
$ ninja
$ ls bin
asm2wasm wasm-as wasm-ctor-eval wasm-dis wasm-emscripten-finalize wasm-metadce wasm-opt wasm-reduce wasm-shell wasm2js
$ cd ~/Documents/arcs
$ /tmp/binaryen/build/bin/wasm-opt demo/pkg/arcs_demo_bg.wasm -o demo/pkg/arcs_demo_bg.wasm-opt.wasm -O
$ echo $?
0 I'm going to keep using this binary locally for now. If it segfaults again I'll update this comment with a backtrace and more info. |
I can confirm that it did help me too (Ubuntu at CircleCI, wasm-pack 0.9.0, rust 1.41.0) |
When building WebAssembly, the invoked wasm-opt command returns a error. To fix this, the current workaround mentioned in the issue rustwasm/wasm-pack#782 is to install wasm-opt manually with npm again.
Using wasm-opt 90 instead of 78 fixed this issue for me (Ubuntu 19.04). Changed version here. |
i'm going to cut a point release today that ups the version of wasm-opt! i'll mention on this issue as soon as i do |
thanks for the prompt response! |
Thanks for fixing the issue guys ❤️ |
Related: #696
🐛 Bug description
Running
wasm-pack build
in in a Github action after running the installer failsTo see a failed build: https://github.com/xldenis/crdocs/runs/421370544?check_suite_focus=true
🤔 Expected Behavior
wasm-opt
should run successfully.👟 Steps to reproduce
Rerunning CI on that specific commit should cause a failure reliably.
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.9.0
The text was updated successfully, but these errors were encountered: