Bugzilla

I note that:
* The WebExtensions process gets a spike in memory and CPU at the start of network requests from the content process.
* When the black frame glitch happens, we don't see much action on the Media threads on WebContent7 process until the network traffic which was started at around 2s in the profile finishes. We then see a surge in processing on the Media threads as decoding happens and then shortly after we get frames displayed. This suggests to me the problem is that the decode pipeline didn't have the data required to produce frames.

Dennis: Can you try disabling all your extensions and trying to repro again?
What are the spec's of the machines on which 


I cannot repro on my 2015 13" MBP (I'm running uBlock Origin there too).

I note that:
* The WebExtensions process gets a spike in memory and CPU at the start of network requests from the content process.
* When the black frame glitch happens, we don't see much action on the Media threads on WebContent7 process until the network traffic which was started at around 2s in the profile finishes. We then see a surge in processing on the Media threads as decoding happens and then shortly after we get frames displayed. This suggests to me the problem is that the decode pipeline didn't have the data required to produce frames.

Dennis: Can you try disabling all your extensions and trying to repro again?

What are the spec's of the machines on which this repro's?

I cannot repro on my 2015 13" MBP (I'm running uBlock Origin there too).