Closed
Bug 470192
Opened 16 years ago
Closed 16 years ago
Garbage collector slow, not aggressive enough, firefox hangs after using >1GB ram
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 468840
People
(Reporter: ernstp, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20081217 Shiretoko/3.1b3pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20081217 Shiretoko/3.1b3pre
Prereq: Firefox 3.1b3
If I start the script here:
http://alteredqualia.com/visualization/evolve/
and watch firefox in the task manager, the memory usage grows quickly.
There is a chance that this will be garbage collected (I guess?) but there's also a chance that firefox grows to > 1GB and stops responding.
Either the garbage collector should be more aggressive or all the garbage shouldn't be produced in the first place. Perhaps some memory could be reused instead?
Happens on Linux too.
Reproducible: Always
Steps to Reproduce:
1. Go to http://alteredqualia.com/visualization/evolve/
2. Start script
3. Watch memory usage increase.
| Reporter | ||
Comment 1•16 years ago
|
||
If you want to get a nice image you can press "Stop" when Firefox reaches 1GB, wait for garbage collection and FF drops back to 50MB, then continue. :-)
| Reporter | ||
Comment 2•16 years ago
|
||
Happens both with and without jit.content, much slower without of cource.
| Reporter | ||
Updated•16 years ago
|
OS: Windows Vista → All
Hardware: PC → All
Version: unspecified → 3.1 Branch
Comment 3•16 years ago
|
||
This seems a duplicate of Bug 468840 or at least strongly related.
| Reporter | ||
Updated•16 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•