Skip to content
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

iOS 11.2.2 Worker error #20

Closed
nickfujita opened this issue Jan 9, 2018 · 4 comments
Closed

iOS 11.2.2 Worker error #20

nickfujita opened this issue Jan 9, 2018 · 4 comments

Comments

@nickfujita
Copy link
Contributor

nickfujita commented Jan 9, 2018

After the iOS 11.2.2 update released Jan 8th 2018 the library is now failing to operate properly, and is throwing the error shown below. It was tested in both the native safari browser and in a web view embedded in an application on device against the sample application in this repo. Any thoughts?

screen shot 2018-01-09 at 6 02 10 pm

@Dador
Copy link
Collaborator

Dador commented Jan 10, 2018

Looks like it's connected to Spectre fixes in browsers.
So I suggest to build with -s ASSERTIONS=1 and see details about error.

Also it can be connected to this bug.

I think running asmjs version for Safari users should work as temporary workaround.

@nickfujita
Copy link
Contributor Author

Confirmed working with just asm.js. From the comments in the bug you linked, the issues persists in 11.2.5 beta, so I'll just stick with asm.js for now. Thanks!

Might be good to leave this open until it gets resolved so others are aware.

@cobarx
Copy link
Collaborator

cobarx commented Oct 8, 2018

Looks like this only affects iOS 11.2.2-11.2.5, 11.3.0 and up should be fine. Adding this for my own notes.

@TheOneric
Copy link
Member

Looks like this only affects iOS 11.2.2-11.2.5

Meaning every affected setup has the ability to upgrade to 11.2.6, which is not affected. Given that and since iiuc it's not something on JSO's side, but rather due to an issue with an early Spectre/Meltdown-fix in iOS, it seems safe to close this now.
If I missed something and there's action required afterall, please say so and the issue will be reopened..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants