Saikrishna Arcot

What's the output when running chromium as `chromium-browser --enable-logging=stderr --log-level=0 --vmodule=vaapi_wrapper=4,vaapi_video_decode_accelerator=4`?

``` vdpau_video: VdpOutputSurfaceCreate(): status 23: The system does not have enough resources to complete the requested operation at this time. ``` Any chance the GPU is running out of memory?

For Nvidia GPUs, `nvidia-smi` is available to print out how much GPU memory each process is using. But assuming nothing else is significantly using GPU memory, something somewhere isn't freeing...

For getting the VAAPI libraries loaded, that should be the only patch needed. There is, however, a bugfix patch (specify-max-resolution.patch) needed for some platforms and hardware for the decoding to...

On my system, 1080p is affected, 720p seems fine.

If I recall correctly, support for Linux V4L2 was added in as part of Wayland on Ozone. I had gotten it to compile once, but the UI didn't appear to...

There was some work done when initially bringing up Wayland on Ozone that excluded the ChromeOS-specific stuff for the regular Linux build. I don't know if that patchset would still...

That's a known/expected issue. Currently, Chromium is compiled with the assumption that it will run on X11. Eventually, I'm hoping I can set the build flag that abstracts the display...

VA-API does work with Wayland; you just have to use a different function to get it initialized (`vaGetDisplayDRM` instead of `vaGetDisplayX11`, I think). There's upstream changes related to Wayland that...

Let me try something to see if it would even work. The change will be in the dev branch.