Verified
Status Update
No update yet.
Comments
ma...@gmail.com
Please ignore the chrome version included in the user agent. I was submitting the bug using Chromium, while the bug itself appears using Google Chrome Version 64.0.3282.140 (Official Build) (64-bit).
ho...@chromium.org
binji@ might have some insight on this.
The issue is related to the implementation of MessagePort + SharedArrayBuffer - AudioWorklet is a customer of both features. Confirmed the repro case works fine on Canary OSX.
I also think this might be relevant:
https://bugs.chromium.org/p/chromium/issues/detail?id=716320
The issue is related to the implementation of MessagePort + SharedArrayBuffer - AudioWorklet is a customer of both features. Confirmed the repro case works fine on Canary OSX.
I also think this might be relevant:
su...@techmahindra.com
[Empty comment from Monorail migration]
bi...@chromium.org
ho...@chromium.org
Per #4: This will be fixed by the resolution of the https://crbug.com/chromium/650937 , so I am marking this as duplicate.
[Monorail components: Blink>Messaging Blink>Workers]
[Monorail components: Blink>Messaging Blink>Workers]
ma...@gmail.com
Hi hongchan, are you sure that issue #650937 (which is a CSS rendering bug) is related to this, or did you link the wrong issue?
an...@gmail.com
I can reproduce the same issue on Version 64.0.3282.186 (Official Build) (64-bit) Mac
ho...@chromium.org
This will be resolved when we have a complete implementation of MessagePort support for SharedArrayBuffer.
ho...@chromium.org
andre.michelle@ machtin.below@
This issue is fixed when "Experimental enabled SharedArrayBuffer support in JavaScript" flag is enabled. Right?
This issue is fixed when "Experimental enabled SharedArrayBuffer support in JavaScript" flag is enabled. Right?
ho...@chromium.org
andre.michelle@ machtin.below@
Ping - I'll wait one more week.
Ping - I'll wait one more week.
ma...@gmail.com
In chrome 66, the original issue seems to be fixed (the SharedArrayBuffer can be received without the deserialization error). However, the example supplied in this report causes the tab to hang, when the page is refreshed 2-3 times (reproducibly).
Shall I file a different bug for this?
Shall I file a different bug for this?
ho...@chromium.org
Could you try it with the latest Canary first? I think the hang issue is fixed in M67.
[Deleted User] <[Deleted User]>
ma...@gmail.com
Canary is not available for linux, but this is still reproducible in Chrome Unstable, Version 66.0.3346.8 (Official Build) dev (64-bit)
ho...@chromium.org
Which issue are we talking about? The MessagePort or the browser hang?
https://omahaproxy.appspot.com/ says all three channels should be M67. Like I mentioned in #12, the fix is in M67. I think you can update the browser or use the dev channel.
ma...@gmail.com
Works with latest dev. Thanks!
ho...@chromium.org
Per #11, the original issue is fixed. Closing.
is...@google.com
This issue was migrated from crbug.com/chromium/809995?no_tracker_redirect=1
[Auto-CCs applied]
[Multiple monorail components: Blink>Messaging, Blink>WebAudio, Blink>Workers]
[Monorail blocked-on:crbug.com/chromium/659037 ]
[Monorail mergedinto:crbug.com/chromium/659037 ]
[Monorail components added to Component Tags custom field.]
[Auto-CCs applied]
[Multiple monorail components: Blink>Messaging, Blink>WebAudio, Blink>Workers]
[Monorail blocked-on:
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
dt...@google.com
Bulk update of issues accidentally marked as duplicate in issue tracker migration (
Description
Steps to reproduce the problem:
1. open chrome://flags
2. make sure that both "Experimental enabled SharedArrayBuffer support in JavaScript" and "Experimental Web Platform features" are enabled.
3. open developer tools
4. in sources tab, make sure that "pause on uncaught exceptions" is checked
5. run the attached example (Also available at
The example starts a worklet and sends a message containing a shared array buffer to the worklet.
What is the expected behavior?
The Worklet should be able to access the data property of the MessageEvent.
What went wrong?
As soon as MessageEvent.data property is accessed on the receiving side, an error "Unable to deserialize cloned data" is thrown.
After that, no further messages are dispatched.
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 64.0.3282.140 Channel: stable
OS Version: 4.13.0-32-generic
Flash Version:
Note that this works fine under Mac OS X using the same build of Chrome (64.0.3282.140)!
Messages that do not contain SharedArrayBuffers do not cause this problem.