-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Safari WASM Range Error #299
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
Comments
I'm not the maintainer, but I've been dealing with a similar issue! This is may be from a bug in webkit (https://bugs.webkit.org/show_bug.cgi?id=200807). Versions of Safari from 13.0 through 13.1.1 have a variety of problems with large wasm files (though I've never seen "call stack size exceeded", that would track with the general pattern of OOMs); it was fixed in webkit 608.3, which I think ships in the most recent Safari. Try e.g. the Safari that runs on iOS 13.1.2, and see if that works! |
Unfortunately it still seems to be broken in the latest beta version of desktop safari (13.0.3), although i agree it sounds like the same issue |
Safari works well with asm file, speed is not worse. |
file size is significantly larger for asm file though |
nginx gzip asm 3mb to 700kb |
I am getting this error as well with all devices using latest safari (Mac OS | iPad OS | iOS) I have discovered if you slow down how fast each operation is occuring on the database, I do not get this error. |
Same issue for me with OS X and iOS and iPad OS using the sql-wasm.js with sql-wasm.wasm while it is working with sql-asm.js. Interestingly I was not able to replicate it with iOS 13 on browserstack. |
Using worker.sql-wasm.js
Version 1.0.0
Error: Unhandled Promise Rejection: RangeError: Maximum call stack size exceeded. (from inside worker.sql-wasm.js)
The same DB file works fine on Chrome and Firefox, and worked before switching to wasm.
Safari Version 13.0.2 (14608.2.40.1.2)
Any ideas?
The text was updated successfully, but these errors were encountered: