safari 26.0 can not handle wasm-exceptions anymore

[mithrendal]

in case anyone wonders and looks into here for help because their emsdk built web apps are not working anymore with apples latest macOS, iPadOS and iPhoneOS...

my two web projects were since years compiled and linked to use the faster and more efficient native wasm-exceptions

My findings:

• compiled and linked with -fwasm-exceptions will crash the web app on startup on apples latest safari 26 while the previous safari versions and all other web browsers still work fine.

I had to rebuild with -fexceptions to make them run also under apples latest safari 26.0

for reference the issue on my project:
vc64web/virtualc64web#285

[mithrendal]

to test a build with the faster native wasm exceptions run https://vamigaweb.github.io/uat/

the build with the about 13% slower javascript-based exceptions you can start with https://vamigaweb.github.io

because vAmigaWeb uses intensively local browser cache to make the app offline capable the best is to open it in a private browser tab to get the current version.

[aheejin]

Can you paste the error message? I don't have Safari 26 available on my Mac yet.

I installed the latest JavaScriptCore (v300391) using jsvu and ran it with a simple program compiled with -fwasm-exceptions, and it ran successfully. I don't think jsvu supports installing older versions (https://webkitgtk.org/jsc-built-products/x86_64/release/ contains only recent versions). So either the problem was fixed at some point or the problem only manifests in the browser setting or is specific to application characteristics.

[mithrendal]

@aheejin

it is here at the green line where an exception is thrown

I will try to step a bit into the entryFunction which is set to in the aboves code _main

UPDATE:

Safari Technology Preview Release 228 (WebKit 21623.1.7.19.1)

also crashes... hope that safari 26.1 fixes it again

[mithrendal]

I opened a bug report at the webkit bug tracker

https://bugs.webkit.org/show_bug.cgi?id=299629