[Webkit-unassigned] [Bug 166480] WebAssembly: test compile / instantiate in a Worker

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Dec 26 12:08:21 PST 2016


https://bugs.webkit.org/show_bug.cgi?id=166480

--- Comment #4 from Saam Barati <sbarati at apple.com> ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > (In reply to comment #0)
> > > > I've heard from someone trying out WebAssembly that they current use compile
> > > > / instantiate in a worker because some implementations aren't asynchronous.
> > > > They want to do work on the main thread while compiling, so a Worker makes
> > > > sense. They then transfer the Module / Instance back to the main thread.
> > > > 
> > > > We should have a test that this works well.
> > > > 
> > > > Related:
> > > >  - WebAssembly: Make WebAssembly.compile truly asynchronous
> > > > https://bugs.webkit.org/show_bug.cgi?id=166016
> > > >  - WebAssembly: Implement the WebAssembly.instantiate API
> > > > https://bugs.webkit.org/show_bug.cgi?id=165982
> > > 
> > > I think this should work as expected regardless of the compile API being
> > > asynchronous internally.
> > 
> > Also, I agree we should have a test for this.
> 
> Right, I want to make sure postMessage-ing Module / Instance / Memory /
> Table all work as expected.

Interesting. Is that the expected behavior? This is unlike anything we do elsewhere. We don't postMessage heap cells since each worker is in a different VM

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161226/1eaed084/attachment.html>


More information about the webkit-unassigned mailing list