Dedicated workers and worklets continue to execute even though documents may be frozen due to the page lifecycle. All threads in a frozen document should be frozen.
Firefox: No public signals
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHgVhZXHsLVLfHpzrTTE4tRg4PhpDvsUDwgOm434WACoooakqg%40mail.gmail.com.
Because the offline audio context is driven entirely from the scheduling in process itself (rather than an external pipeline like realtime audio). You should find that they do pause correctly. The worklet/worker scheduler end up pausing execution themselves which then makes it work for OfflineAudioContext.
dave.--On Tue, May 14, 2019 at 1:49 PM Raymond Toy <rt...@chromium.org> wrote:As we've discovered, WebAudio's OfflineAudioContext's don't pause. And there's currently no API to pause these.I think that they probably should. If the offline context is rendering a large number of samples and the graph has a ScriptProcessorNode or AudioWorkletNode, then there could be potentially a huge number of tasks posted to the main thread or other threads/workers. I assume that's not what you want.We'll need some guidance here on what you really need so we can come up with a way to pause/resume these.dtap...@chromium.org https://github.com/WICG/page-lifecycle/pull/35 Specification: https://github.com/WICG/page-lifecycle/pull/35 https://github.com/WICG/page-lifecycle/pull/35 Considered a bug part of freezing lifecycle that was underspecified. Dedicated workers and worklets continue to execute even though documents may be frozen due to the page lifecycle. All threads in a frozen document should be frozen.--Some risk for pages that might be doing work in workers where they will see their workflow paused. eg. A background worker uploading or downloading files. Firefox: No public signals Edge: No public signals Safari: No public signals Web developers: No signalsYes Yes https://wpt.fyi/results/lifecycle/worker-dispay-none.tentative.html?label=master&product=chrome%5Bexperimental%5D&product=edge&product=firefox%5Bexperimental%5D&product=safari%5Bexperimental%5D&aligned https://www.chromestatus.com/features/5276568928649216
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHgVhZXHsLVLfHpzrTTE4tRg4PhpDvsUDwgOm434WACoooakqg%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAHgVhZVRoYdK%2BoBcGm1wcUhSFYAF0kK25gaqhU8HU3-9QpK1zA%40mail.gmail.com.