Isolated Web Content 2 has * "MTG::MediaTrackGraphStableStateRunnable ControlMessage"s occurring for the entire period. * 5 x MDSM::Seek markers with associated MDSM::StateChange - COMPLETED. MDSM::PlayStateChanged - PLAY_STATE_ENDED occurs before each seek. These likely correspond to the reloads. The Remote Data Decoder process has a VPXDecoder decoding frames for the first 1.5s. Isolated Web Content 1 appears to be the trigger for RDD as it has "PlayVideo" markers for 1.5s and then MDSM::EnterVideoSuspend, but VideoSink::RenderVideoFrames markers repeat for the entire period. If this occurs again, logging can be [added to a profile](https://blog.paul.cx/post/profiling-firefox-media-workloads/#the-media-preset), which may would more info: 1. Load about:logging 2. Logging preset: "Media playback" 3. Ensure "Logging to the Firefox Profiler" is checked. 4. "Start Logging" 5. Reload the mp4. 6. "Stop Logging". New tab is opened after a few seconds, showing Profiler. 7. "Upload Local Profile". 8. Include everything, but most importantly "hidden threads". 9. Upload. 10. Paste URL here. 11. If you are able to identify in about:processes the process ID corresponding to the tab with the mp4, then that would help in finding it in the profile, if there are multiple tabs open.
Bug 1922848 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Isolated Web Content 2 has * "MTG::MediaTrackGraphStableStateRunnable ControlMessage"s occurring for the entire period. * 5 x MDSM::Seek markers with associated MDSM::StateChange - COMPLETED. MDSM::PlayStateChanged - PLAY_STATE_ENDED occurs before each seek. These likely correspond to the reloads. The Remote Data Decoder process has a VPXDecoder decoding frames for the first 1.5s. Isolated Web Content 1 appears to be the trigger for RDD as it has "PlayVideo" markers for 1.5s and then MDSM::EnterVideoSuspend, but VideoSink::RenderVideoFrames markers repeat for the entire period. If this occurs again, logging can be [added to a profile](https://blog.paul.cx/post/profiling-firefox-media-workloads/#the-media-preset), which would have more info: 1. Load about:logging 2. Logging preset: "Media playback" 3. Ensure "Logging to the Firefox Profiler" is checked. 4. "Start Logging" 5. Reload the mp4. 6. "Stop Logging". New tab is opened after a few seconds, showing Profiler. 7. "Upload Local Profile". 8. Include everything, but most importantly "hidden threads". 9. Upload. 10. Paste URL here. 11. If you are able to identify in about:processes the process ID corresponding to the tab with the mp4, then that would help in finding it in the profile, if there are multiple tabs open.