From: "Manfred Gahr"
Also eine Lösung dazu kann ich euch nicht bieten. Aber vielleicht ein paar Vermutungen. Bei mir ist das ähnlich. Auf einem Athlon 800 mit 256MB Speicher brauchte X nach 2 Stunden Arbeit am Rechner ca. 100MB. Nach einem Speicherupgrade auf 512MB braucht es nun plötzlich 220MB(!!) [..] Woran das genau liegt, ob es Bug (Speicherleck) oder Feature(Caching von Grafikdaten, Zwischenspeichern von verdeckten Fenstern.....) ist kann ich leider nicht sagen...
von http://www.linuxpower.org/display.php?id=211 "Keith Packard, in his TinyX server using his new frame buffer code, has reduced the X server to 500-700K bytes of code (depending on whether you want his new render extension for anti-aliased text and graphics). Most of the perception of bloat is caused by how Linux reports memory. An X server maps the display card into its address space, and on current graphics cards this can easily be 8, 16, 32 or even 64 megabytes of address space (for the frame buffer and registers of the display). Naive people look at "ps" or "top" and draw the wrong conclusion. Clients may be asking the X server to preserve pixmaps on their behalf (which should really be charged to the client, but it shows up in the X server). So, for example the RSS size on my iPAQ is 2.2 megabytes when running Familiar, with backing store and save unders still enabled (arguably, on a device like an iPAQ, I should disable them, which would further reduce the RAM footprint)." Alfred