Bug 279949 – Safari WASM tail calls/garbage collection still somewhat broken in iOS 18/macOS Sequoia

• Status: NEW
• Component: WebAssembly

[Tony Hursh]

Guile Hoot is an implementation of Guile (Scheme) in WASM. Until recently, it hasn't worked in Safari because tail calls and garbage collection weren't available.

This appears to be fixed in Safari Technology Preview Release 203 (Safari 18.0, WebKit 20620.1.6) but is still broken with regular Safari in the new macOS 15 and iOS 18.

Steps to reproduce:

Visit:

https://spritely.institute/news/hoot-wireworld-live-in-browser.html

and:

https://spritely.institute/news/building-interactive-web-pages-with-guile-hoot.html

with different Safari versions.


Results:


Technology Preview 203: both work.


Desktop Safari Version 18.0 (20619.1.26.31.6):

https://spritely.institute/news/hoot-wireworld-live-in-browser.html works. There is a warning about about a CORS problem, but I think that is unrelated.

https://spritely.institute/news/building-interactive-web-pages-with-guile-hoot.html fails with "Unhandled Promise Rejection: CompileError: WebAssembly.Module doesn't parse at byte 12: 0th type failed to parse because array types are not enabled"


Mobile Safari 5.0 (iPhone; CPU iPhone OS 18_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.0 Mobile/15E148 Safari/604.1:

Both fail with "Unhandled Promise Rejection: CompileError: WebAssembly.Module doesn't parse at byte 12: 0th type failed to parse because array types are not enabled"

I suspect that this is due to the latest STP 203 enhancements not making the cutoff for the release of iOS 18/macOS Sequoia, but just wanted to get it on record.

[Ahmad Saleem]

@Tony - I am unable to access any of these links to reproduce the issue? Can you confirm whether it can be access or they are restricted in any way (geo restriction)?

[Ahmad Saleem]

(In reply to Ahmad Saleem from comment #1)
> @Tony - I am unable to access any of these links to reproduce the issue? Can
> you confirm whether it can be access or they are restricted in any way (geo
> restriction)?

Ignore - it worked after few minutes (so it might be some connectivity issue on my end).

[Radar WebKit Bug Importer]

<rdar://problem/136724587>