https://bugzilla.novell.com/show_bug.cgi?id=197990 ------- Comment #18 from federico@ximian.com 2006-09-21 11:59 MST ------- Conversation with Keith Packard that may be useful for debugging: (12:40:45) keithp: federico: xrestop probably doesn't measure window pixmaps (12:40:53) keithp: federico: it also won't measure regions (12:41:15) keithp: So, one possibility is that it's creating a region with *lots* of tiny rectangles and kcompmgr isn't cleaning up correctly (12:41:33) keithp: Alternatively, it's creating really big windows somehow and they're getting stuck in pixmaps (12:41:56) keithp: federico: about the only way you'll figure it out is to instrument the X server and see where the memory is going (12:45:17) keithp: federico: window trees are stored in pixmaps as a part of Composite (12:45:27) keithp: federico: damage is the piece tracking areas modified by rendering (12:45:42) keithp: so, damage may have huge regions, and Composite may have huge pixmaps (12:46:44) federico: keithp: so you are saying that there are two kinds of pixmaps - normal pixmaps from clients and Composite pixmaps, but xrestop does not report the latter? (12:49:05) keithp: federico: right, they're not really visible to clients by ID, so they don't show up So if it's indeed a kompmgr problem, you may need to hack the X server to pinpoint the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.