Saikrishna Arcot

There shouldn't be any significant increase in disk writes, unless you have logging enabled at some verbose level.

The `vdpau-va-driver` doesn't have VP9 support, and only supports H264.

Regarding the appimages, I've published a couple of new appimages [here](http://vps.saiarcot895.cloudns.pro/appimages/dev/). Use 78.0.3902.4 if your glibc version is 2.16 or newer (Ubuntu Xenial or newer), or 81.0.4000.3 if your glibc...

Just to check, is it still using the GPU video decoder with 4K videos?

That message doesn't mean Chromium thinks you're running on Windows; that message means that hardware decoding for protected (DRM) video is restricted to some Intel and and GPUs on Windows...

If you start playing from the beginning again, does it get fixed? I've seen this happening as well, but without any hardware acceleration involved.

The output that you're getting with the iHD driver is similar to #83.

If you use `LIBVA_DRIVER_NAME=i965 chromium-browser --enable-logging=stderr --loglevel=0 --use-gl=desktop`, do you see a bunch of Skia shader compilation error messages on the command prompt output?

The ANGLE gl driver is a bug; it's not supposed to be using that.

Nothing in the packaging itself should be causing this bug. I suspect it's in Chromium or in the libva libraries on 20.04; I don't know which yet.