Using mozilla-1.2.1-r4, phoenix-bin-0.5, xfree-4.2.1-r2, gcc 2.95.3 Problem: When viewing ~700 kB jpeg images, each time you click on a new image, memory usage of X goes up 12 MB (based off of command 'top -d.5' and pressing M to sort by memory usage). However, when clicking back button and subsequently viewing another ~700 kB jpeg image, memory usage of X goes up by another 12 MB. This continues until all available RAM (256MB) is used and then swap begins to be filled. No noticable slowdowns occur. However, once most of the swap is full (1 GB in my case) Mozilla will freeze and crash. Immediately after crashing, memory used by X returns to a low value (32MB in my case). This occurs with BOTH mozilla and phoenix. While using Konqueror, this problem does not occur. Increase in memory usage of X by 12MB does occur, but the memory seems to be flushed every 4-6 images. This seems to be the proper behaviour we should see. This has been confirmed on other Gentoo boxes (don't have other Linux boxes to see if it is distro dependant). Only reason I have brought it up here is that if you compile phoenix from source (same version, just not from ebuild), the problem DOES NOT occur, therefore I guess its a gentoo specific problem. To test, you can go to the same website I did (some guy's vacation photos on a university server): http://expert.ics.purdue.edu/~wu01/TRIP-CA/ I can provide any other necessary details if needed. Extremely reproducible. Often once it begins using swap, mozilla will freeze using all available CPU and slowly consume all available system memory/swap until dying once no memory is available or I kill mozilla-bin.
Through bugzilla.mozilla.org and discussions with the developers of Mozilla, this problem has been fixed, but is available in only the nightly builds. We'll all just have to wait until 1.3_final or 1.4 (whatever is next).
They cannot send us a patch ?
http://bugzilla.mozilla.org/show_bug.cgi?id=188581 I'm not sure if there is a patch available, except if you pour through the CVS logs...that link is for the Mozilla bug I submitted, and they seem to reference other similar bugs (particularly Mozilla Bug 174760). Possible patch in Mozilla Bug 179498.
Yep, bug #179498 has a patch, and seems to work.
Added patch to mozilla-1.2.1-r5. Thanks!
Just want to mention that for me (original reporter) mozilla-1.2.1-r5 works perfectly! THANKS
