Closed Bug 664128 Opened 12 years ago Closed 12 years ago
JS heap grows continually when www
.gamespot .com is left idle due to insufficiently frequent GC
User-Agent: Mozilla/5.0 (Windows NT 5.2) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.91 Safari/534.30 Build Identifier: Mozilla/5.0 (Windows NT 5.2; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 Firefox accumulates memory indefinitely after visiting a website. Reproducible: Always Steps to Reproduce: 1. Disable all plugins 2. Close Firefox 3. Start Firefox and check for enabled plugins. If there are such go to step 1, else close Firefox and continue to step 4 4. Start Firefox in safe mode 5. Maximize the Firefox window 6. Navigate to gamespot.com 7. Click "Click here to continue to GameSpot" on the page 8. Wait the next page to load fully 9. Minimize the Firefox window Actual Results: Increase of the Firefox memory usage - after about 4 hours and 20 min the private memory of Firefox reached 500 MB. The following image obtained with Process Monitor shows the memory usage of Firefox for that time interval: http://img221.imageshack.us/img221/2010/firefoxmemoryusage4hourb.png Expected Results: Constant or near constant memory usage within a reasonable bound. I didn’t observe accumulative memory usage pattern with Google Chrome 12.0.742.91. I instructed Firefox to generate nspr log file in the beginning. Leak Gauge didn't find leaks in this log file. The attachment contains the information from about:memory obtained at the end of the test.
Step7 isn't necessary for me to reach the main page. I can confirm that the used memory increased from ~80mb to over 200mb until I stopped. tested with FF4.01 and disabled plugins and in the safemode
Status: UNCONFIRMED → NEW
Ever confirmed: true
Sounds like this might be a dup of bug 656120. The GC isn't triggered while firefox is idle. You could try the ff6 pre beta and see if the memory goes back down if you click GC + CC on about:memory. It has to be done in ff6 as the update to about:memory didn't exist before.
Thanks for the precise steps to reproduce!
Summary: Unbounded increase of the Firefox memory usage after loading website → JS heap grows continually when www.gamespot.com is left idle due to insufficiently frequent GC
Hector, can you try a Nightly build? Bug 656120 was fixed and that will hopefully help a lot.
I installed Firefox build from 22-Jun-2011 on Windows XP (x86) and performed the steps. The memory usage (Working Set) of Firefox did not exceed 141 Mb for 9 hours interval: http://img24.imageshack.us/img24/9255/firefoxgamespotcom9h.png The Kernel Time of the Firefox process at the end of the test was 24 minutes. What is the reason for this?
(In reply to comment #8) > I installed Firefox build from 22-Jun-2011 on Windows XP (x86) and performed > the steps. The memory usage (Working Set) of Firefox did not exceed 141 Mb > for 9 hours interval: > > http://img24.imageshack.us/img24/9255/firefoxgamespotcom9h.png Great! Time to declare victory :) > The Kernel Time of the Firefox process at the end of the test was 24 > minutes. What is the reason for this? I guess Firefox is making some system calls. One possibility is the url-classifier, which periodically downloads new information about malware sites from a server. See bug 650649 for more details.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.