(As such it does not occur in stable/candidate channels, that do not
have VAAPI merged in.)
We don't have much of a delta about hwacc with upstream right now, it's
mostly patches for Ozone (which doesn't get used in Xorg, correct me if
I'm wrong) and then the chromium.launcher that simply turns on some flags.
Daniel, thanks a lot for guiding the debugging on this, and Andreas for
carrying the debugging out.
I thought incorrectly that this was already stated: The leak does not
happen with VAAPI disabled
---> features= VaapiVideoDecod er,VaapiVideoEn coder,VaapiVide oDecodeLinuxGL
chromium
--disable-
<---
(As such it does not occur in stable/candidate channels, that do not
have VAAPI merged in.)
We don't have much of a delta about hwacc with upstream right now, it's
mostly patches for Ozone (which doesn't get used in Xorg, correct me if
I'm wrong) and then the chromium.launcher that simply turns on some flags.
Patches: /git.launchpad. net/~chromium- team/chromium- browser/ +git/snap- from-source/ tree/build/ chromium- patches/ optimization? h=dev /git.launchpad. net/~chromium- team/chromium- browser/ +git/snap- from-source/ tree/launcher/ chromium. launcher? h=dev#n128
https:/
Flags:
https:/