tag 285761 + help
retitle 285761 memory leak -- how to distinguish from Mozilla memory leaks?
thanks
Hi,
Jerome Alet [EMAIL PROTECTED] - Fri, Feb 04, 2005:
I'm currently on holidays and can't do the same tests
feel free to close the bug
Well, I can't think of a way to help
Le jeudi 03 février 2005 à 17:53 +0100, Loïc Minier a écrit :
Hi,
This is a followup for Debian bug http://bugs.debian.org/285761.
[EMAIL PROTECTED] - Wed, Feb 02, 2005:
It may be useful to run xrestop for this. Note: If you just run
top,
...
could you try loading a lot
Hi,
This is a followup for Debian bug http://bugs.debian.org/285761.
[EMAIL PROTECTED] - Wed, Feb 02, 2005:
It may be useful to run xrestop for this. Note: If you just run
top,
...
could you try loading a lot of images without browsing much and
compare the X memory usage, maybe
Hi
I cannot tell for the first report but the one that show galeon
making X use 180M may be the same problem as:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288073
mozilla: It would be nice if Mozilla freed X pixmaps instead of
leaking them
It would be nice if Mozilla (/Firefox) were to
Package: galeon
Version: 1.3.18-2
Followup-For: Bug #285761
It also happens to my galeon installation.
PID SZ SZRSS VSZ%MEM
15012 285628 82112 68416 328448 28.6
That is with only one blank window open (after closing the ones I was
browsing on).
X proccess was using 180MB
5 matches
Mail list logo