Closed
Bug 684718
Opened 13 years ago
Closed 13 years ago
Extremely high memory usage (about 450k +)
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: searchfgold67899, Unassigned)
Details
(Whiteboard: [closeme 2011-11-01])
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.1) Gecko/20100101 Firefox/6.0.1
Build ID: 20110830092941
Steps to reproduce:
Leaving Firefox 6.0 open for more than an hour or two.
Actual results:
Extremely high memory usage after some time, amounting to 450 or 500k sometimes.
Expected results:
Firefox should not have used that much memory.
Reporter | ||
Comment 1•13 years ago
|
||
By 450 to 500k I meant 450,000 to 500,000 k (:
Comment 2•13 years ago
|
||
Sorry, you really have to give more details. What websites were open ? How many tabs ? What add-ons do you use ?
Comment 3•13 years ago
|
||
Also post or attach the contents of about:memory when the memory usage is high.
Leaving open without you touching it, so idle? What is 500k? Isn't it 500 MB?
See Bug 656120 and Bug 661527. Comment if you do not think this covers your problem. See if Firefox gets killed because it allocates more than 2GB on Win 32bit.
Reporter | ||
Comment 5•13 years ago
|
||
QUOTE: What websites were open? How many tabs? What add-ons do you use?
Only Yahoo open. One tab. Only Adblock Plus and a Homeschool Gadget toolbar.
QUOTE: Also post or attach the contents of about:memory when the memory usage is high.
Thank you, will-do.
QUOTE: What is 500k? Isn't it 500 MB?
500,000k = 500 MB = yes
QUOTE: See Bug 656120 and Bug 661527. Comment if you do not think this covers your problem.
They do not have to do with my problem. I don't know what the second one is about at all, and the first one is for Firefox 4.0.
QUOTE: See if Firefox gets killed because it allocates more than 2GB on Win 32bit.
Thank you for your suggestion. How do I do that?
Leave it open unattended for several hours (like 10+). If the memory usage still grows until OS kills it, then it should be one of those bugs (they are actually the same). The solution to those bugs is included only in Firefox 7. That is also something you could test.
Comment 7•13 years ago
|
||
You should try with newer versions of Firefox (7 or 8), where there are a lot of improvements in memory usage.
Updated•13 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•