well, i tried to check something within the last few hours. here's what i experienced:
at one point there was (nearly at the beginning of my x session) a moment that x used
about 70% of my memory. when i killed sylpheed-claws, it got back to about 20%.
but then after a few hours (well, when i woke up at the morning i noticed it), x used
about 40% of my memory again, so i tried to check what went wrong.
i killed gaim. gaim swapped a long time, but after this (even after a couple of
minutes), X' memory usage was still the same. so i decided to kill EVERY single x app.
and nothing helped. not to kill mozillafirebird, not to kill all my terminals and so
on. i checked for a zombie via top command, but there was only one defunced netstat
process. so in the ende there was no app running related to x, but the basic gnome
processes. i killed the gnome-panel, then i killed metacity: nothing. its still the
same. the only change from killing metacity is that X is using 10% MORE of my ram
*lol* (metacity restarted automatically after killing, of course). but i dont think
gnome itself is the matter, since i got this problem already within kde and fluxbox a
while ago.
so there's only two options:
a) its gtk itself. i think i never testes kde/fluxbox for a "long" time without gtk
apps.
b) its X itself. thats what i believe now...
could it be something went wrong when compiling xfree? maybe there's some cflags i
should change to compile xfree or something... overtuned, undertunes flags? i didnt
use that many optimizations. if i remember correctly i always used:
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -pipe"
CXXFLAGS="${CFLAGS}"
if it matters, some machine specs here:
amd athlon xp 1800+
msi k7t turbo -R (via kt133a chipset plus promise softraid)
512mb pc133 sdram
creative 3dblaster ti (geforce4 ti4200)
creative soundblaster live player 1024
well.. the rest would be only hard drives and so on (simple udma100)...
any help welcome :-)
arne
--
[EMAIL PROTECTED] mailing list
