New comment by pbui on void-packages repository

https://github.com/void-linux/void-packages/pull/23511#issuecomment-656798149

Comment:
@ericonr Yes, the old patch which @Duncaen is referring to (and removed in06430645c61fe9ee0b8c052c6d58b0cd0bab4d61) enabled vaapi unconditionally.  As noted in this commit message, this is no longer the case.  First, we no longer have a big vaapi patch; vaapi support is now provided by upstream chromium.  Second, vaapi is OFF by default.  The user must explicitly choose to enable it.  This should address the problem @Duncaen mentioned.

Note, I introduced this build option in 88464d1272e6a98f2a045169c07446a3181f5df9 and have been using it since then for my own machines.  I am requesting to enable it by default because I believe it is stable now.

That said, I've only tested this on machines with Intel GPUs (both with it on and off).  I'd be happy to wait for feedback from users with different devices.

Final note: Arch Linux has enabled vaapi by default in a similar manner as to what I am proposing here: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium&id=0cbb8c4205a73ceb76066477fef42e55ae5aa394