Log reason if VA-API cannot be used used
Categories
(Core :: Graphics, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox99 | --- | fixed |
People
(Reporter: pmenzel+bugzilla.mozilla.org, Assigned: stransky)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
Start Nightly (99.0a1, 20220222190424) with
MOZ_LOG="PlatformDecoderModule:1" MOZ_DISABLE_RDD_SANDBOX=1 nightly
and start BigBlueButton WebRTC video conference application, which uses VP8, and my graphics device supports decoding VP8, and that worked in the past.
Actual results:
According to sudo intel_gpu_top
the Intel graphics device is not used for decoding. The reason is not logged on the console with MOZ_LOG="PlatformDecoderModule:1"
. Only success messages for H264 are logged:
libva info: VA-API version 1.13.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_13
libva info: va_openDriver() returns 0
Expected results:
If VA-API cannot be used for some reason, a message should be logged on the terminal.
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 2•3 years ago
|
||
Please run with MOZ_LOG="PlatformDecoderModule:5" evn variable.
Assignee | ||
Updated•3 years ago
|
Reporter | ||
Comment 3•3 years ago
|
||
Yes, I know, that it’s logged with level 5, but the common case is, too not see to much “spam” I normally start with level 1, then I see something does not work, but I am in a video conference, I cannot quit. After quitting and restarting Nightly, the problem might not reproducible.
Also, I’d say, that if success messages are logged in level one, error messages should too. (In my opinion errors should be logged by default without an environment variable set.)
Reporter | ||
Comment 4•3 years ago
|
||
Happened right now. In the session with WebRTC, in a separate tab playing https://test-videos.co.uk/vids/jellyfish/webm/vp8/720/Jellyfish_720_10s_30MB.webm, VA-API wasn’t used according to sudo intel_gpu_top
.
Restarting Nightly with MOZ_LOG="PlatformDecoderModule:5"
VA-API is now used for https://test-videos.co.uk/vids/jellyfish/webm/vp8/720/Jellyfish_720_10s_30MB.webm.
Assignee | ||
Comment 5•3 years ago
|
||
The log will be available under 'MediaFormatReader' entry where HW acceleration is disabled after decoder crash.
Assignee | ||
Comment 6•3 years ago
|
||
Updated•3 years ago
|
Reporter | ||
Comment 7•3 years ago
|
||
Thank you. The patch looks good.
Comment 9•3 years ago
|
||
bugherder |
Description
•