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
2024-09-21T19:50:57.044057Z INFO calling wasm-opt
2024-09-21T19:50:58.448578Z ERROR ❌ error
error from build pipeline
Caused by:
0: HTML build pipeline failed (2 errors), showing first
1: error from asset pipeline
2: wasm-opt call to executable '/Users/gilescope/.cargo/bin/wasm-opt' with args: '["--output=/Users/gilescope/git/dotsamaworld/target/wasm-opt/release/app-25b623b3922d6169_bg.wasm", "-Oz", "/Users/gilescope/git/dotsamaworld/dist/.stage/app-25b623b3922d6169_bg.wasm"]' returned a bad status: signal: 11 (SIGSEGV)
Error: error from build pipeline
wasm-opt version 116 (version_116) (same for versions back to 105 that I could easily try)
If >=0.2.87 is using a newer version of wasm-opt then it could well be something in the c/c++ of wasm opt project where the problem is rather than here.
The text was updated successfully, but these errors were encountered:
I tried reverting #3463 on top of master but it didn't seem to be the cause. If not that I'm not sure what's causing it. (underlying problem is that wasm-opt isn't written in rust!)
Considering the segfault, this looks like a problem in wasm-opt to me rather then in wasm-bindgen.
It might of course turn out that there is some faulty output coming from wasm-bindgen, but that would be hard to investigate without even a proper error message.
Describe the Bug
On an arm based m3 mac (and in docker as amd86), versions above 0.2.86 lead to a core dump in wasm-opt.
Smoking PR is likely this one: #3463
Steps to Reproduce
At least the code is open source to reproduce this one:
trunk build --release
( https://trunkrs.dev/ )Expected Behavior
should compile cleanly and optimise wasm cleanly.
Actual Behavior
Additional Context
wasm-opt version 116 (version_116)
(same for versions back to 105 that I could easily try)If >=0.2.87 is using a newer version of wasm-opt then it could well be something in the c/c++ of wasm opt project where the problem is rather than here.
The text was updated successfully, but these errors were encountered: