wasm-pack results in SIGSEGV on Ubuntu 23.04

[Akirathan]

Yesterday, I updated to Ubuntu 23.04 and was unable to build WASM with ./run gui build --skip-wasm-opt since, as wasm-pack process resulted in SIGSEGV during "Installing wasm-bindgen" phase. I tried using newer wasm-pack - 0.11.0, but got the same result. With wasm-pack 0.9.1 I was able to build the WASM, but unable to execute it in the browser.

The problem seems to be related to the system libcurl. On my system, Ubuntu 23.04, it helped to remove libcurl4-openssl-dev and install librust-curl-dev, and libcurl4-gnutls-dev instead. Now I can build the IDE without any problems.

This problem seems ubiquitous. People mostly dealt with it by downgrading to wasm-pack 0.9.1, but we cannot do that on Enso. Some related references:

• 65214 segmentation fault (core dumped) wasm-pack help rustwasm/wasm-pack#823
• Segmentation Fault when checking for update rustwasm/wasm-pack#997
• wasm-pack build segfaults in Docker rustwasm/wasm-pack#1079

I hope this might help anybody with Ubuntu that has not upgraded yet to 23.04.

[MichaelMauderer]

I ran into this a while ago and there is an old post in our discord.
My workaround was to use the static-curl feature: cargo install wasm-pack --features curl/static-curl

[JanBeelte]

I also ran into this yesterday and fixed it by running:
cargo install wasm-pack --version="^0.10" --no-default-features
not sure which one is the better solution though :-)

[MichaelMauderer]

Yes, exactly. Seems to be an issue with system dependencies in wasm-pack.

[wdanilo]

That's terrible. Anyway, in such a case, I believe that @MichaelMauderer hot fix is better, as it allows us to use the newest version of wam-pack. @MichaelMauderer could you double-confirm that cargo install wasm-pack --features curl/static-curl is good enough, and if so, could you please add it to our installation instructions with a short description why its needed, please? :)

[MichaelMauderer]

Now I was trying to reproduce the issue to double-check the solution... but I cannot trigger the default any more. It might be my last system update fixed the issue due to an update to the broken decency?

@JanBeelte What is your OS and openssl version?

[MichaelMauderer]

I redact my statement. The downgraded version, from yesterday, fails today. Maybe the binary was cached somewhere? No matter, cargo install wasm-pack --features curl/static-curl --version="=0.10.2" solved it again, and I'll open a PR with a note to the docs.

[JanBeelte]

That's terrible. Anyway, in such a case, I believe that @MichaelMauderer hot fix is better, as it allows us to use the newest version of wam-pack. @MichaelMauderer could you double-confirm that cargo install wasm-pack --features curl/static-curl is good enough, and if so, could you please add it to our installation instructions with a short description why its needed, please? :)

I think you have a miss understanding here I only used --version="=0.10.2" because your build script forced me to do so.