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

Tracking SharedArrayBuffer status #4

Closed
mulderr opened this issue Jan 5, 2018 · 3 comments
Closed

Tracking SharedArrayBuffer status #4

mulderr opened this issue Jan 5, 2018 · 3 comments

Comments

@mulderr
Copy link
Member

mulderr commented Jan 5, 2018

Due to Meltdown/Spectre all major browser vendors are temporarily disabling SharedArrayBuffer by default.

Importantly:

This is a temporary measure until other mitigations are in place.

Until then this breaks nanosleep which is using SAB explicitly.

@mulderr
Copy link
Member Author

mulderr commented Aug 1, 2018

According to the information here:

SharedArrayBuffer will be re-enabled in Chrome versions where Site Isolation is on by default.

Chrome 67 seems to have site isolation on by default and link below suggests Chrome 68 re-enables SAB. (yay!)

Some comments here suggest Firefox does not have a plan yet but they are discussing it. Until then SAB has to be enabled manually.

Edge... do we care?

@mulderr
Copy link
Member Author

mulderr commented Aug 1, 2018

Closing. Firefox may still take a while but new versions of Chrome should work out of the box so there's an easy solution to point people to.

@mulderr mulderr closed this as completed Aug 1, 2018
@ElvishJerricco
Copy link
Member

Great news. I'm pretty hopeful that this will be on by default in every major browser within the year, so I don't mind closing this.

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

No branches or pull requests

2 participants