[plug] memory

[Craig Ringer]

> Some apps like to allocate shared memory with X and never release it. 
> Old mozilla builds were a big culprit of this. Try having top running as 
> you go about your business, see what causes a rise and when.
> 
> Of course, you /do/ have 35MB of free RAM, its not as if the system is 
> going down in a heap - but X using ~200mb of RAM is not a happy thing.

Some more info:

Just for a ballpark comparison, my X server is using 3.8 % of my RAM, or 
about 9.5M on a 256M machine. Can't tell you off the top of my head what 
the one at home uses but I think its closer to 20mb (NVidia driver) on a 
512M machine.

Either way, a 200mb X server is /silly/ and means something is leaking, 
either in the X server or via Xshm allocations etc - its usually the 
latter.

Running various apps alone and trying to determine which causes the 
problem can be useful.

BTW that X server RAM usage was with nothing serious running except Mozilla.

craig at fred$ xlsclients
fred  gkrellm
fred  /usr/apps/ROX-Filer/Linux-ix86/ROX-Filer -p=mine
fred  xconsole -file .xsession-errors
fred  licq
fred  /usr/bin/x-terminal-emulator
fred  /usr/lib/mozilla/mozilla-bin -mail


-- 
Craig Ringer
GPG Key Fingerprint: AF1C ABFE 7E64 E9C8 FC27  C16E D3CE CDC0 0E93 380D
	-- if it ain't broke, add features 'till it is. (or:)
	while (! broken) { features ++ ; broken = isBroken(features) }