That's tens of gigabytes of pixmap memory so there's a major leak.
Let's say this is definitely a bug in Chromium, but arguably a bug in
Xorg for not responding while it frees the massive amount of leaked
memory.
** Changed in: xorg-server (Ubuntu)
Importance: High => Undecided
** Changed in
So I took some screenshots of `xrestop` while chromium was in the google
meet.
There was an "unknown PID" listed, but given other characteristics of
that line, I assume that it is related to chromium.
Here are some of the columns over time:
Pxms MiscPxm memTotal
12:09:28
Wow, that doesn't look like a loop unless Chromium had leaked an out-of-
control number of pixmaps. Please use 'xrestop' to see what the pixmap
count and other resource usage of Chromium is before it's closed. If
that's the issue then we might also want to check to see if the leak is
due to our hwa
I attached gdb to xorg while the bug was happening (100% cpu usage after
closing chromium), and got the backtrace with symbols. I hope this
helps, but maybe it missed the loop, I don't know.
** Attachment added: "xorg.backtrace"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/203343
Found it, and I closed it because the screen flickering is gone:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448
But the "Atomic update" error was there, on pipe A if that makes any
difference. I see it on A/B/C, very much like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/180
> "Atomic update failure" may also be specific to the OLED panel that it
> looks like Andreas is using. I have one of those but have never run Xorg
> on it.
FWIW, I'm using two external 4k Dell monitors via usb-c, plus the laptop
panel also at its max resolution (a bit lower then the monitors:
288
I suggest installing the Xorg debug symbols and then attaching gdb to it
while it's using 100% CPU. Do that a few times and you should get a good
idea of the stack trace.
A lazier way to do it would be to just kill Xorg with a fatal signal,
upload the resulting crash file (ubuntu-bug /var/crash/..
In comment #10 there are some instances of "Atomic update failure" that
go for a few minutes each. I don't know how to disable atomic KMS in
Xorg. It's easy to toggle in Wayland but apparently this bug doesn't
exist in Wayland.
And I don't think mentions of "nouveau" are relevant to Andreas.
** P
"Atomic update failure" may also be specific to the OLED panel that it
looks like Andreas is using. I have one of those but have never run Xorg
on it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.n
9 matches
Mail list logo
