Bug 1170958 introduces a stream chain within DOMMediaStream that according to bug 1170958 comment 82 breaks the AsyncLatencyLogger. We can fix it by reporting the stream chain in DOMMediaStream to the logger.
So, first, we should make sure it still works. It's been ages I haven't used it. Ping me on irc if you need help with that, it's not very complex.
I've used this much more recently than paul, and also have an (unlanded) update to the analysis script that UI used extensively a while back.
Randell, if you attach that script and some instructions for how to use the AsyncLatencyLogger here, I'll take a look at wiring it back up, thanks.
leaving NI open to remind me.
Priority: -- → P2
Reminder to me to dig out the script
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.