Description of problem: Since chromium-73-*, video playback doesn't work if it's accelerated through VAAPI. Version-Release number of selected component (if applicable): chromium-73.0.3683.86-2.fc30.x86_64 How reproducible: Always (might be hardware specific) Steps to Reproduce: 1. Install chromium 2. Install vaapi driver for your platform - I've tested libva-intel-driver-2.3.0-2.fc29.x86_64 3. Play random video on youtube Actual results: Playing videos does not work unless you disable VAAPI. Expected results: Video playback should work even with VAAPI enabled. Additional info: I am testing it on T470s on random youtube videos, so vainfo outputs: vainfo: VA-API version: 1.4 (libva 2.4.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.3.0 On about:gpu, I have Video Decode: Hardware accelerated . On about:media-internals, I see MojoVideoDecoder as video_decoder . On about:media-internals, there are repeating messages when VAAPI is enabled: pipeline_state kSuspending pipeline_state kSuspended event SUSPENDED pipeline_state kResuming I'd have tested H264/H265 playback, but that's not supported on Fedora Chromium build and I am not sure if installing chromium-libs-media-freeworld wouldn't invalidate the testing. So I am testing it on VP9 videos on hardware that supports VP9 HW decoding.
Only hardware accelerated VP9 decoding is broken and only on Intel GPUs. Can you please attach a log by running `chromium-browser --log-level=0 --enable-logging=stderr --v=1 2>&1 | tee chromelog.log`?
Created attachment 1550919 [details] chromium-browser --log-level=0 --enable-logging=stderr --v=1
Log attached, I don't see anything suspicious there though :/ Last bunch of errors: [1801:1801:0402/103325.334121:INFO:CONSOLE(0)] "Unchecked runtime.lastError: No current window", source: chrome-extension://jldhpllghnbhlbpcmnajkpdmadaolakh/background.html (0) started to appear when I closed the chromium window but didn't kill the process yet.
> I don't see anything suspicious there though It was expected. We need to do a full debug build (https://chromium.googlesource.com/chromium/src/+/master/docs/linux_debugging.md). Unless we know the reason why it is failing, I can't open a bug report upstream. They will close it as not supported. On top of that I don't have an Intel GPU to test.
Broken on Coffee Lake as well. Interestingly, not broken on Bay Trail (CherryView in vainfo).
https://github.com/intel/intel-vaapi-driver/issues/456 Not broken on Skylake either, but have also observed it being broken on Coffee Lake. I'm using chromium-vaapi vs chromium-browser though.
Similar here, not broken on Skylake, but broken on Gemini Lake.
@Tom , I think we need to disable vaapi. I am hearing reports that 75 just broke h.264 acceleration on some Intel GPUs. For everyone else who need video acceleration may use chromium-vaapi from RPMFusion. We should keep the official package out of this mess. I seriously don't know what upstream is doing.
FEDORA-EPEL-2019-b94f559810 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b94f559810
chromium-75.0.3770.100-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b94f559810
I request everyone to test and report vaapi playback from latest chromium-vaapi in RPMFusion testing.
(In reply to Akarshan Biswas from comment #11) > I request everyone to test and report vaapi playback from latest > chromium-vaapi in RPMFusion testing. So, video playback in chromium-vaapi-75.0.3770.100-2.fc30.x86_64 works, but it's *not* hardware accelerated. Is it necessary to change any settings in about:flags? I see "Hardware-accelerated video decode" as enabled.
(In reply to František Zatloukal from comment #12) > (In reply to Akarshan Biswas from comment #11) > > I request everyone to test and report vaapi playback from latest > > chromium-vaapi in RPMFusion testing. > > So, video playback in chromium-vaapi-75.0.3770.100-2.fc30.x86_64 works, but > it's *not* hardware accelerated. Is it necessary to change any settings in > about:flags? I see "Hardware-accelerated video decode" as enabled. Share your chrome://gpu
Created attachment 1587362 [details] about:gpu / Intel Corporation HD Graphics 620
(In reply to František Zatloukal from comment #14) > Created attachment 1587362 [details] > about:gpu / Intel Corporation HD Graphics 620 Everything is fine. video is hardware accelerated if it's supported by your GPU. I found no such errors.
I am doing tests on youtube videos, so VP9. It is supported by my gpu (tested also in VLC) : $ vainfo | grep VP9 libva info: VA-API version 1.4.1 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_4 libva info: va_openDriver() returns 0 VAProfileVP9Profile0 : VAEntrypointVLD VAProfileVP9Profile0 : VAEntrypointEncSlice VAProfileVP9Profile2 : VAEntrypointVLD But I am still getting ton of dropped frames and CPU utilization reaching almost 100% while watching random 4k/60fps content on youtube. I'll attach screenshot shortly with stats overlay on yt.
Created attachment 1587373 [details] YouTube Performance Overlay - screenshot
Can you switch (In reply to František Zatloukal from comment #17) > Created attachment 1587373 [details] > YouTube Performance Overlay - screenshot Can you switch to iHD driver?
(In reply to Akarshan Biswas from comment #18) > Can you switch (In reply to František Zatloukal from comment #17) > > Created attachment 1587373 [details] > > YouTube Performance Overlay - screenshot > > Can you switch to iHD driver? Okay, launching chromium-vaapi with ihd driver fixed the performance problem. So with chromium-vaapi-75.0.3770.100-2.fc30.x86_64 , launched with LIBVA_DRIVER_NAME=iHD chromium-vaapi , video playback works just fine and is HW accelerated. I guess there isn't an easy way for an app to prefer the ihd driver over the legacy one on supported platforms? Anyway, thanks!
(In reply to František Zatloukal from comment #19) > (In reply to Akarshan Biswas from comment #18) > > Can you switch (In reply to František Zatloukal from comment #17) > > > Created attachment 1587373 [details] > > > YouTube Performance Overlay - screenshot > > > > Can you switch to iHD driver? > > Okay, launching chromium-vaapi with ihd driver fixed the performance problem. > > So with chromium-vaapi-75.0.3770.100-2.fc30.x86_64 , launched with > LIBVA_DRIVER_NAME=iHD chromium-vaapi , video playback works just fine and is > HW accelerated. > > I guess there isn't an easy way for an app to prefer the ihd driver over the > legacy one on supported platforms? > > Anyway, thanks! Put this in /etc/profile `export LIBVA_DRIVER_NAME=ihd`
FEDORA-EPEL-2019-931a6c5c69 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-931a6c5c69
chromium-75.0.3770.100-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-931a6c5c69
chromium-75.0.3770.100-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Akarshan Biswas from comment #20) > Put this in /etc/profile > > `export LIBVA_DRIVER_NAME=ihd` Yeah, I've meant if it cannot be done in the package itself?