Package Details: chromium-vaapi 74.0.3729.157-1

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL: https://www.chromium.org/Home
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 66
Popularity: 3.220646
First Submitted: 2016-07-09 09:44
Last Updated: 2019-05-15 08:33

Dependencies (47)

Required by (44)

Sources (10)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

maximbaz commented on 2019-03-21 10:45

Sadly new version doesn't solve the issue. Foreigncon, I'll try to look into it but not promising any results... If someone can reproduce VP9 issue and wants to help, please don't hesitate to try to help debugging this.

enihcam commented on 2019-03-21 04:32

73.0.3683.86 is released with one decoder fix.

Changelog: https://chromium.googlesource.com/chromium/src/+log/73.0.3683.75..73.0.3683.86?pretty=fuller

Foreigncon commented on 2019-03-20 05:23

@maximbaz. Hmm. That make sense. Can you please try debugging with this https://chromium.googlesource.com/chromium/src/+/master/docs/linux_debugging.md ?

maximbaz commented on 2019-03-19 18:04

I might have some proof against this being a driver issue:

  1. VP9 decoding works if I downgrade to chromium 72
  2. I tried both drivers LIBVA_DRIVER_NAME=i965 chromium and LIBVA_DRIVER_NAME=iHD chromium, the behavior is exactly the same in both cases.

That Github issue I'm following :) because I want to switch to iHD driver, and that issue prevents you from fast-forwarding the videos, i.e. if you open a video, it plays fine, but as soon as you try to fast-forward, the video gets stuck.

But in chromium 73 the video doesn't even begin to play :(

Thanks for your insights!

Foreigncon commented on 2019-03-19 17:48

@maximbaz that means it's probably related to the driver. Also I found this issue.

Also the error log that you've mentioned is normal and is unrelated.

Without knowing how the vp9 videos are failing I won't be able to come up with a plan. :(

maximbaz commented on 2019-03-19 17:14

There's only one log entry in chrome://gpu, I'm not entirely sure it's related:

[13172:13172:0319/140608.218200:ERROR:sandbox_linux.cc(364)] : InitializeSandbox() called with multiple threads in process gpu-process.

And there are no errors in console if I start chromium from terminal :(

Foreigncon commented on 2019-03-19 16:02

@maximbaz Thanks. Do you get any errors in chrome://gpu logs section? There are a lot of changes including a new vp9 encoder.

maximbaz commented on 2019-03-19 13:07

Thanks for your help! Given that there's a 4h build between debug attempts, I'm happy to run the tests for you if you have some ideas.

Disabling MojoVideoDecoder didn't help, I see "GpuVideoDecoder" in chrome://media-internals, but VP9 videos don't play as well :(

Foreigncon commented on 2019-03-19 12:42

@maximbaz. I will look for changes in vaapi_vp9_accelerator.cc file from 72 and 73. I don't have an intel GPU so can't debug. Chromium is running just fine on my both of my PCs running amdgpu.

Meanwhile try disabling Mojo using the flag --disable-features=MojoVideoDecoder

maximbaz commented on 2019-03-18 18:20

Foreigncon: just tried, the problem persists :(