[Linux/EGL] Hardware decoding into dmabuf results in errors
Categories
(Core :: Audio/Video: Playback, defect, P5)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox77 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | disabled |
firefox80 | --- | disabled |
firefox81 | --- | fixed |
People
(Reporter: kubrick, Assigned: stransky)
References
(Blocks 2 open bugs, Regression)
Details
(Keywords: regression)
Attachments
(3 files)
Trying to play YT videos with then new widget.wayland-dmabuf-video-textures.enabled pref set to true (default), results to stuttering, green frames and eventually errors.
[vp9 @ 0x7fa6aabda000] get_buffer() failed
[vp9 @ 0x7fa6aabda000] thread_get_buffer() failed
Config:
widget.wayland-dmabuf-vaapi.enabled=true
widget.wayland-dmabuf-video-textures.enabled=true
media.ffvpx.enabled
Updated•4 years ago
|
Reporter | ||
Comment 1•4 years ago
|
||
Duplicate of bug 1645671 and bug 1645673
Assignee | ||
Comment 2•4 years ago
•
|
||
Can you try to check if Bug 1629788 makes any difference here (i.e. test some former nightly)?
Thanks.
Reporter | ||
Comment 3•4 years ago
|
||
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 4•4 years ago
|
||
@stransky, I'm not sure what revision you want me to test but I had no issue with commit 1ed52478a3599f41ff05d2fc57eb5586aae622e5 (I don't use nightly because of bug 1430775, so I patch and build my own version, sigh)
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Set release status flags based on info from the regressing bug 1629788
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 6•4 years ago
|
||
Why https://hg.mozilla.org/mozilla-central/rev/e9de35da7a75c9fd9ec6ca13d45030c55faf1148 ?
Now I can't use vaapi...
Comment 7•4 years ago
•
|
||
VAAPI depends on dmabuf-video-textures - which is not finished yet (bug 1629788 comment 27). Without this patch you had to enable both prefs to use VAAPI. (Brief regressions are expected to happen on Nightly. Other patches still await review.)
Updated•4 years ago
|
Assignee | ||
Comment 8•4 years ago
|
||
This should be a dupe of Bug 1645671.
Reporter | ||
Comment 9•4 years ago
|
||
I have tried D85152, which fixes Bug #1645671, but apart from the green frames, the other errors reported here are still not fixed:
Playing VP9 videos on youtube results in poor plaback quality, youtube swithing to lower quality, and eventually displaying an error message "An error occurred. Please try again later"
Assignee | ||
Comment 10•4 years ago
|
||
(In reply to Francois Guerraz from comment #9)
I have tried D85152, which fixes Bug #1645671, but apart from the green frames, the other errors reported here are still not fixed:
Playing VP9 videos on youtube results in poor plaback quality, youtube swithing to lower quality, and eventually displaying an error message "An error occurred. Please try again later"
Please attach MOZ_LOG="PlatformDecoderModule:5" log from your build where Bug 1645671 is fixed.
Thanks.
Comment 11•4 years ago
|
||
I could retest bug 1643855 comment 9 if you could you trigger a try build of bug 1645671. Otherwise I'll wait for autoland.
Reporter | ||
Comment 12•4 years ago
|
||
D85152, fresh profile, with:
media.ffmpeg.vaapi-drm-display.enabled=true
media.ffmpeg.vaapi.enabled=true
media.ffvpx.enabled=false
security.sandbox.content.level=0
Comment 13•4 years ago
|
||
Indeed, bug 1645671 comment 23 fixed green frames, but YouTube decoding errors persist with (U)HD VP9 and HD H264.
MOZ_LOG="PlatformDecoderModule:5" MOZ_ENABLE_WAYLAND=1 mozregression --repo autoland --launch bacacb384008 --pref media.ffvpx.enabled:false media.ffmpeg.vaapi.enabled:true -a https://addons.mozilla.org/en-US/firefox/addon/enhanced-h264ify/ -a https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ -a https://www.youtube.com/watch?v=Yds5jgqmYpE -P stdout
1:15.02 INFO: b'[h264 @ 0x7fc56bdc5800] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2'
1:15.02 INFO: b'[h264 @ 0x7fc56bdc5800] get_buffer() failed'
1:15.02 INFO: b'[h264 @ 0x7fc56bdc5800] thread_get_buffer() failed'
1:15.02 INFO: b'[h264 @ 0x7fc56bdc5800] decode_slice_header error'
1:15.02 INFO: b'[h264 @ 0x7fc56bdc5800] no frame!'
Updated•4 years ago
|
Comment 15•4 years ago
|
||
It's the same error I saw in bug 1643855 comment 9.
0:28.57 INFO: b'[h264 @ 0x7fdd5e5cc000] get_buffer() failed'
0:28.57 INFO: b'[h264 @ 0x7fdd5e5cc000] thread_get_buffer() failed'
0:28.57 INFO: b'[h264 @ 0x7fdd5e5cc000] decode_slice_header error'
Assignee | ||
Updated•4 years ago
|
Comment 16•4 years ago
|
||
From a short test, software decoding with media.ffmpeg.dmabuf-textures.enabled seems to work fine. So much thanks as always!
comment 0 and comment 12 anyway have VAAPI enabled:
(Francois Guerraz from comment #0)
Config:
widget.wayland-dmabuf-vaapi.enabled=true
widget.wayland-dmabuf-video-textures.enabled=true
media.ffvpx.enabled
Assignee | ||
Comment 17•4 years ago
|
||
Please re-test when Bug 1656436 lands.
Thanks.
Assignee | ||
Updated•4 years ago
|
Reporter | ||
Comment 18•4 years ago
|
||
Now this is working incredibly well!
Thank you ♥
Updated•4 years ago
|
Description
•