This is now released to beta and edge.
And thank you, Jianhui, for contributing the fix!
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu
Great, thanks for your continued testing on this bug report!
I'm pushing it to beta as well.
--
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 gigabyte
Chromium played a local video just fine, and that video was recognized
like this by mpv:
(+) Video --vid=1 (*) (h264 1920x1080 60.000fps)
--
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/203
I used that snap in a few long calls already, and did not experience the
Pxms leak. Closing the browser after such calls also did not leave xorg
at 100% cpu like before.
Haven't checked x264 playback yet, but as Daniel said, I doubt it would
regress because of this patch.
--
You received this bu
I will, but just to update expectations: Each revision of Chromium in
beta and edge need to be manually reviewed because of a new plug[1].
So expect some a couple of days of delay. Or install it manually from
[2].
[1]
https://forum.snapcraft.io/t/request-for-personal-files-interface-in-chromium-
Please ping here when a new chromium snap is available in latest/edge.
--
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 Xo
Sounds coincidental judging by the simplicity of the patch.
--
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)
I'm committing this to edge only as there are reports of H264 failure in
the upstream tracker. Let's see if we can reproduce it.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Upstream bug got an update:
https://bugs.chromium.org/p/chromium/issues/detail?id=1467689#c41
Patch?
https://chromium.googlesource.com/chromium/src/+/42d57d016f5fb6d2a1a354743b9be911c1be87e8%5E%21/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
A fixing was prepared and will updated on chromium issue.
--
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)
This bug is easy to reproduce, what we need now is a fix ;)
--
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)
My understanding is 'top' is able to show graphics memory allocations at well.
There maybe also drm tools can show the graphics memory usage.
I will reproduce more on this issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubu
The output from `top` was always well behaved while chromium was open,
until it was closed, at which point xorg cpu's usage went through the
roof.
The test case here is indeed watching "Pxms" in xrestop while chromium
is displaying hw accelerated video.
--
You received this bug notification beca
Still, making Xorg think there's a massive pixmap leak is causing it to
become unresponsive while it frees them all when Chromium exits.
Also, would 'top' show graphics memory allocations at all?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
I captured the 'top' and `xrestop` as attachment.
The `xrestop` show quite a lot memory usage, but it is not aligned w/ `top`.
`top` shows no obvious memory leak.
** Attachment added: "all-status.png"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2033433/+attachment/5700188/+fil
I try the self build Chromium 118.0.5966.0, and run below command for h264 hw
decoding.
After 30min playback, the chromium is well.
```shell
./src/out/Default/chrome --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --use-fake-ui-for-media-stream
--vmodule=*/ozone/*=1,*/wayland/*=1,*/
** Tags added: kivu
--
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 vide
Oh! Intel and Google already know about it: https://crbug.com/1467689
** Description changed:
+ https://crbug.com/1467689
+
+ ---
+
chromium 118.0.5966.0 2604 latest/edge
Whenever I use chromium in a video session (meet, youtube) that used
hardware acceleration
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
<---
Is there a way to disable VAAPI in Chromium to see if that stops the
leak?
--
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 th
Thanks for guiding the troubleshooting on this one, I learned a new tool
;) (xrestop)
--
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 pix
** Summary changed:
- Xorg 100% CPU and frozen desktop after closing chromium
+ Chromium leaks tens of gigabytes of pixmaps (in the Xorg process)
** Summary changed:
- Chromium leaks tens of gigabytes of pixmaps (in the Xorg process)
+ Chromium leaks tens of gigabytes of pixmaps (in the Xorg pro
22 matches
Mail list logo
