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:59 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244526@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#36) by Robert O'Callahan (Mozilla) on W3C Bugzilla. Mon, 09 Jul 2012 03:14:26 GMT

(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.

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

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