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.
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.