Profiler doesn't capture gecko log properly when playing a local video file
Categories
(Core :: Gecko Profiler, defect, P3)
Tracking
()
People
(Reporter: alwu, Unassigned)
References
Details
STR.
- download this videowhich is from bug 1905022
- go to
about:loggingand selectMedia playbackpreset - start profiling
- open new tab and play the video you downloaded from the step1.
- make the video playing for 1 second
- go back to
about:loggingand stop profiling
Expect.
7. We should see logging in the MediaDecoderStateMachine thread
Actual.
7. No logging can be seen in the MediaDecoderStateMachine thread
This shows an issue which is when playing a local file media, the logging won't be captured by Firefox profiler. If you play a file over internet, eg. https://bug1905022.bmoattachments.org/attachment.cgi?id=9409858. Then you can see that logs will be captured successfully.
I tried to capture a profile with a local video like you suggested and I managed to get log messages. Here's an example profile: https://share.firefox.dev/3SjkDIy
Am I doing something differently? Could you check one more time to see if you can reproduce the issue?
| Reporter | ||
Comment 2•1 year ago
|
||
So this seems a Windows only issue. I tried it again on the latest Nightly and the issue still exists. No logging can be found in this profile.
| Reporter | ||
Comment 3•1 year ago
|
||
Recently we have received more profiled results which are apparently lacking the necessary information. Eg. in bug 1904394 comment11, it lacks of the debug logs.
Another one from an user who was helping me profiling a Youtube issue. The weird thing for that is no any media threads captured in the Youtube tab (pid: 15636). But by looking the GPU process, the media threads and logs was indeed captured. According to the reporter, this situation only happens when the certain Youtube problem appears (video stutter for a several seconds)
Nazım, would you think of any possible reasons of missing the debug log, or entire threads and logs for the profiler? Thank you!
I couldn't get back to this yet, sorry about that. Hopefully I should be able to look at it soon. But it also feels like it might not be profiler related issue.
Comment 5•10 months ago
|
||
I believe the root cause of this is the same as bug 1914388 and considering that it's fixed, this one should be fixed as well.
@Alastor could you confirm if this is fixed now?
| Reporter | ||
Comment 6•10 months ago
|
||
I can confirm this issue no longer happens on the latest Nightly, close this bug.
Description
•