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 hwacc patches.
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
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:
Xorg 100% CPU and frozen desktop after closing chromium
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
