Closed Bug 966873 Opened 10 years ago Closed 9 years ago
Stream Graph keeps consuming CPU for Audio Nodes in BFCache when not connected to destination
+++ This bug was initially created as a clone of Bug #941873 +++ Load this in a tab and then load another page in the same tab. Expected results: cpu drops after loading the second page. Actual: cpu use continues for many minutes. FWIW Chrome behaves as expected.
It seems that this bug is already fixed. Or at least I cannot reproduce this issue with the latest nightly. The CPU goes down immediately after the changing of the content in the same tab.
That's because I made it so that AudioContext::Suspend is called from nsGlobalWindow::SuspendTimeouts, that is called when the page is changed. AudioContext::Suspend (among other things) moves all the MediaStreams that belong to the suspended AudioContext to a separate array (different from MediaStreamGraphImpl::mStreams, which is the array of streams to be processed). Then the AudioContext is collected some time after.
Does it mean that this bug is fixed? Or do we have to do something more?
I think it's fixed, yes.
I'm not sure this is the correct bug ID.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Yes, I don't think it was bug 815492 that fixed this, but good to know it is fixed, thanks.
You need to log in before you can comment on or make changes to this bug.