[chromium-discuss] When SharedArrayBuffer will be back? I don't find any info.

[Antony]

I'm developing a quite complex webapp and I'm using a couple WebWorkers to
compute heavy stuff in parallel.

All these workers are sharing data with few SharedArrayBuffers. The shared
data are pretty big in size (>100MB) and the workers needs a synchronous
way to access it. I guess this is the most common use case when using
WebWorkers :).

Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place"
(https://www.chromium.org/Home/chromium-security/ssca).

Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of weeks,
months...? I can't release my app for now :/

I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?

Thanks guys!!
Antony

[Colxi]

I'm interested too, about any progress on this subject.Webworkers are a
game changer.

Post by Antony
I'm developing a quite complex webapp and I'm using a couple WebWorkers to
compute heavy stuff in parallel.
All these workers are sharing data with few SharedArrayBuffers. The shared
data are pretty big in size (>100MB) and the workers needs a synchronous
way to access it. I guess this is the most common use case when using
WebWorkers :).
Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place" (
https://www.chromium.org/Home/chromium-security/ssca).
Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of weeks,
months...? I can't release my app for now :/
I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?
Thanks guys!!
Antony

[Pawel Misiurski]

I'm also waiting for return. It's a total must for my browser game
bad.city. Once execution queue is busy, postMessage is being executed with
massive delays. Probably that's because of very busy requestAnimationFrame.
Even with transferable objects there's always a delay. SharedArrayBuffer
should be enabled by default for immune processors.

Post by Colxi
I'm interested too, about any progress on this subject.Webworkers are a
game changer.

Post by Antony
I'm developing a quite complex webapp and I'm using a couple WebWorkers
to compute heavy stuff in parallel.
All these workers are sharing data with few SharedArrayBuffers. The
shared data are pretty big in size (>100MB) and the workers needs a
synchronous way to access it. I guess this is the most common use case when
using WebWorkers :).
Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place" (
https://www.chromium.org/Home/chromium-security/ssca).
Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of
weeks, months...? I can't release my app for now :/
I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?
Thanks guys!!
Antony

[Antony]

Yes I also use transferable objects for now, but all my input data must be
duplicated in all web workers and it takes 3x the memory (I reach easily
1GB). SharedArrayBuffer was so perfect for my application.
In my app, the webworkers don't modify the shared data between each other,
but they just need the same input data. It is a pity that I need to
duplicate all the input buffers, what a waste of memory :)

[Ugur Ister]

Yeah, it would be great to get SharedArrayBuffer reenabled soon and/or get
an update on the to be expected timeline/date if available.

Post by Antony
I'm developing a quite complex webapp and I'm using a couple WebWorkers to
compute heavy stuff in parallel.
All these workers are sharing data with few SharedArrayBuffers. The shared
data are pretty big in size (>100MB) and the workers needs a synchronous
way to access it. I guess this is the most common use case when using
WebWorkers :).
Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place" (
https://www.chromium.org/Home/chromium-security/ssca).
Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of weeks,
months...? I can't release my app for now :/
I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?
Thanks guys!!
Antony

[Anthony Bowker]

Re-enabling SharedArrayBuffer is being tracked here
https://bugs.chromium.org/p/chromium/issues/detail?id=821270

Post by Antony
I'm developing a quite complex webapp and I'm using a couple WebWorkers to
compute heavy stuff in parallel.
All these workers are sharing data with few SharedArrayBuffers. The shared
data are pretty big in size (>100MB) and the workers needs a synchronous
way to access it. I guess this is the most common use case when using
WebWorkers :).
Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place" (
https://www.chromium.org/Home/chromium-security/ssca).
Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of weeks,
months...? I can't release my app for now :/
I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?
Thanks guys!!
Antony

[Ugur Ister]

thanks Anthony, very helpful and can't wait for it to be brought back, will
allow us so many more cool things in our projects.

Post by Anthony Bowker
Re-enabling SharedArrayBuffer is being tracked here
https://bugs.chromium.org/p/chromium/issues/detail?id=821270

Post by Antony
I'm developing a quite complex webapp and I'm using a couple WebWorkers
to compute heavy stuff in parallel.
All these workers are sharing data with few SharedArrayBuffers. The
shared data are pretty big in size (>100MB) and the workers needs a
synchronous way to access it. I guess this is the most common use case when
using WebWorkers :).
Bad luck, all browsers removed the SharedArrayBuffer because of the
security issues, but the Chrome team mentioned that "this is intended as a
temporary measure until other mitigations are in place" (
https://www.chromium.org/Home/chromium-security/ssca).
Unfortunatly, *I don't find any info regarding the return of the
SharedArrayBuffer, does someone have some info?* is it a matter of
weeks, months...? I can't release my app for now :/
I'm suprised because webworkers are useless without SAB. Maybe there is a
workaround I don't know about?
Thanks guys!!
Antony