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

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 Jul 2012 05:16:38 +0000
Message-Id: <E1So6Ks-0003wW-4V@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #38 from Grant Galitz <grantgalitz@gmail.com> 2012-07-09 05:16:37 UTC ---
(In reply to comment #37)
> (In reply to comment #36)
> > 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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 9 July 2012 05:16:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 July 2012 05:16:39 GMT