[Webkit-unassigned] [Bug 190552] New: UI / DOM blocks audio thread, causing crackles
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sat Oct 13 09:14:56 PDT 2018
https://bugs.webkit.org/show_bug.cgi?id=190552
Bug ID: 190552
Summary: UI / DOM blocks audio thread, causing crackles
Product: WebKit
Version: Other
Hardware: iPhone / iPad
OS: iOS 12
Status: NEW
Severity: Major
Priority: P2
Component: Web Audio
Assignee: webkit-unassigned at lists.webkit.org
Reporter: ae at seven.systems
We're developing a WebAudio-based DAW running in a WKWebView. This works amazingly well and we're thrilled how far the Web Audio API has come.
However, when the engine is under high load (roundabout 500 nodes for the entire loaded project), interacting with the DOM (scrolling, adding / removing elements, etc.) in any way causes severe buffer underruns, even at 1024 frames buffer size (set by starting another app that sets that buffer size and records in the background).
Shouldn't the audio thread run with high priority and not be blocked by the UI / DOM thread?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20181013/7d8ddf8a/attachment.html>
More information about the webkit-unassigned
mailing list