1613070 - Add tracing markers to AudioWorklet code (real-time thread side)

Status: RESOLVED FIXED

(Core :: Web Audio, task, P2)

Description

[Paul Adenot (:padenot)]

I've had this locally for some time, but I want people to be able to give me traces (now that Nightly is clearly usable for testing).

Two new trace points: the ProcessBlocksOnPorts method of the AudioWorkletEngine, and just around calling process, to be able to gauge overhead and catch any non-determinism (I think we'll be able to remove one of the two later).

Comment 1

[Paul Adenot (:padenot)]

Attachment: Bug 1613070 - Add tracing markers to AudioWorklet code (real-time thread side). r?karlt

Moving the trace point for messages to the inner loop allow understanding what
pages are doing better, it is important to be able to characterize onmessage
calls.

Having two tracepoints under ProcessBlockOnPorts allows gauging the buffer
preparation overhead. vs just the page's processing code.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/279fba56ed01
Add tracing markers to AudioWorklet code (real-time thread side). r=karlt

Comment 3

[Oana Pop-Rus]

https://hg.mozilla.org/mozilla-central/rev/279fba56ed01