336668 - Bon Echo causes X.org Leak

Status: RESOLVED INCOMPLETE

(Firefox :: Shell Integration, defect)

Description

[Brad Allen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060504 Firefox/2.0a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060504 Firefox/2.0a1

As I use Bon Echo more and more, Xorg's VM footprint grows. With significant use over about 24 hours, X.org grew from 85 MB to 250 MB. Opening this page- http://www.improveverywhere.com/mission_view.php?mission_id=48 - Which is filled with jpg images, caused it to grow from 90 MB to 135 MB just now. Closing the tab or window does not free it, but closing Bon Echo does.

Reproducible: Always

Steps to Reproduce:
1. Note X.org's VM usage
2. Open Bon Echo
3. Go to http://www.improveverywhere.com/mission_view.php?mission_id=48
4. Note X.org's new VM usage
Actual Results:  
Xorg grew from 85 to 130 MB, which was not recoverable until I closed Bon Echo.

Expected Results:  
Xorg to not fill up or to have the RAM freed.

I have browser.sessionhistory.max_total_viewers set to 4, I have browser.cache.memory.capacity set to 131072, and I don't have any extensions other than DOM installed. I have mplayer, flash, java, acrobat, and vlc plugins installed, none are actively being used. Built Bon Echo using configure options --prefix=/usr --enable-xinerama --enable-default-toolkit=gtk2 '--enable-optimize=-pipe\ -w\ -O2\ -DDEBIAN\ -mtune=athlon-xp\ -march=athlon-xp\ -msse2'. Using X.org 6.8.2 on Ubuntu 5.10.

Comment 1

[Brad Allen]

Tested using 1.0.8 and a friend who had 1.5.0.3. Both were using Ubuntu 5.10. On both, closing the tab did not result in X.org freeing the RAM. I'd like to note that if Firefox is caching the page, there should be no need for X.org to store a copy of the images as well.

Comment 2

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!

Comment 3

[Carsten Book [:Tomcat]]

-> Closing as incomplete because of missing feedback if this is still reproducible in the latest release (Firefox 2.0.0.4) or Trunk Build.