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 free X pixmaps sometimes, instead of leaking all bitmaps it allocates. While it's true I have a gigabyte of ram, I often go to pages with images on them, and even with a gig it doesn't take more than a few minutes before firefox has consumed all memory and is running the X server into swap. How to reproduce: 1. Load mozilla or firefox. 2. Load a page with images 3. Hold down shift and press reload 4. Look, it just leaked all the x pixmaps. It may be useful to run xrestop for this. Note: If you just run top, the memory will show up under the X server, since it's an X pixmap that Mozilla is leaking. Rate of leak: This depends primarily on how fast Mozilla can allocate pixmaps. Reloading a huge photo gallery off of localhost, I am able to leak an impressive 70MB every 3 seconds. :-) I eagerly await news of how Mozilla doesn't do this on other peoples' computers. :-) " could you try loading a lot of images without browsing much and compare the X memory usage, maybe using xrestop to check pixmap mem usage. I do not see this leak so it may be a mozilla bug only. the other leak me be fixed too. I only use 65M of physical memory for 130M of virtual memory. It is not bad as i have a few tabs opened. Cheers Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
