W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:57 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244528@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#37) by Grant Galitz on W3C Bugzilla. Mon, 09 Jul 2012 05:16:37 GMT

(In reply to [comment #37](#issuecomment-24244526))
> (In reply to [comment #36](#issuecomment-24244523))
> > Also the UI thread being blocked from other tabs is experienced on a
> > per-browser basis for me at least, with Chrome in the clear actually.
> 
> It may depend on how many tabs you have open and what they contain, but sooner
> or later Chrome will put multiple tabs onto the same main thread.

True

To sum up my argument: We are currently not provided all the resources inside a webworker to attain full independence from the main thread yet, and dependence on the main thread kills us with i/o lag.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/113#issuecomment-24244528
Received on Wednesday, 11 September 2013 14:36:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC