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 ---> chromium --disable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiVideoDecodeLinuxGL <--- (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: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/build/chromium-patches/optimization?h=dev Flags: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/launcher/chromium.launcher?h=dev#n128 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
