Closed Bug 257016 Opened 21 years ago Closed 20 years ago

Firefox leaks X Windows Resources

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 259672

People

(Reporter: bugzilla, Assigned: bugzilla)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040301 Firefox/0.8 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040301 Firefox/0.8 I've been having problems with mplayer complaining it couldn't allocate X resources on my home system. The problem would fix itself if I closed Firefox and restarted it from which I surmise there was a resource leak. Today I ran xrestop to monitor resource usage and saw mozilla-firefox was using 49Mb of X resources. The galeon browsers which I also use didn't use nearly as much so I conclude the problem is with firefox itself rather than Gecko. The X resource leak only seems to go up when I visit sites with images, using squirel mail doesn't cause any leakage. Reproducible: Always Steps to Reproduce: 1. run xrestop 2. monitor resource usage opening new tabs and then closing them Actual Results: These are some results from todays experiment with a brief description of what I was doing. res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier startup 2c00000 71 38 1 32 26 426K 4K 430K ? Home Page - Mozilla Firefox webmail 2c00000 104 38 1 81 39 593K 5K 598K ? SquirrelMail 1.2.6 - Mozilla Firefox open'ed LWN in tab 2c00000 126 38 1 90 49 672K 5K 678K ? LWN: Kernel development - Mozilla Firefox open'ed LJ friends in tab 2c00000 143 38 1 114 52 1130K 6K 1136K ? People I watch - Mozilla Firefox surfed a bit, closed LJ tabs 2c00000 163 38 1 134 60 1412K 7K 1420K ? LWN:Kernel development - Mozilla Firefox googled mozilla firefox-bugzilla, went to mozilla homepage 2c00000 178 38 1 160 64 1822K 7K 1830K ? mozilla.org - home of mozilla, firefox, thunderbird, and ca browsed through pages to bugzilla 2c00000 178 38 1 177 63 4419K 7K 4427K ? mozilla.org Bugzilla -- the Mozilla bug database - Mozilla created bugzilla account 2c00000 183 38 1 177 60 4419K 7K 4427K ? UserPreferences - Mozilla Firefox browsed a few bugs, gave up, shut tabs 2c00000 175 38 1 177 60 4419K 7K 4427K ? LWN:Kernel development - Mozilla Firefox read some mail, went to house.co.uk, closed additional tabs 2c00000 170 38 1 223 60 5902K 7K 5909K ? SquirrelMail 1.2.6 - Mozilla Firefox Read more mail, browsed around LWN, back to 2 tabs 2c00000 170 38 1 223 60 5902K 7K 5909K ? SquirrelMail 1.2.6 - Mozilla Firefox Expected Results: X resource usage should return to baseline after I've opened and then closed tabs I was browsing in instead of slowly climbing.
On my cooker system at home the same problem seems to exist. Running "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040716 Firefox/0.9.2" and with only the bugzilla page open Firefox seems to be using: 2800000 212 44 1 1056 82 20089K 8K 20098K ? Bug 257016 - Firefox leaks X A lot of X resources.
Searching through the bugs, I found a few others that I thought at first described my problem, but this is definitely the worst symptom. It even affects my epiphany. After a while of browsing, if many images have been visited, virtual memory for either Firefox or Epiphany will have increased slightly, but X memory will have grown almost three times as fast. And when I close all windows with images, X's memory usage does not decrease. It is only when I close all instances of the browser does it memory usage return to normal. I am in Slackware 10 with X.org 6.8.1 (as packaged by the Dropline Gnome distribution). I am using Firefox 1.0 preview release. Epiphany is 1.4.1, if that helps.
This looks like it might be related to or a symptom of: https://bugzilla.mozilla.org/show_bug.cgi?id=213391 which describes a failure to evict cache entries.
See also bug #259672 -- these may be dupes of each other.
*** Bug 293333 has been marked as a duplicate of this bug. ***
Marking dup of bug 259672 since it has more technical information (and a dependency) *** This bug has been marked as a duplicate of 259672 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.