Closed
Bug 515079
Opened 16 years ago
Closed 16 years ago
memory leak 1 gb of RAM during paused pandora session, uncommon
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: scnerd, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 4.0.20506)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 4.0.20506)
Had a paused, signed-in session on Pandora, noticed the my computer was running out of ram, and found that firefox was using almost 1 GB. That session of Firefox had been running through a few stand-by's, a hibernate, and at times had a dozen or so tabs open. When I noticed the leak, though, I only had pandora and a two other text pages open their own tabs, and the amount of memory being consumed was increasing.
Reproducible: Couldn't Reproduce
Steps to Reproduce:
1.I'm sorry, I don't know. I couldn't find what happened that made it go bad. Just go to Pandora.com and maybe mess with the browser for a while. See the details for what I had been doing with the browser, if you want to try to reproduce it.
Actual Results:
nothing unusual really. The page loaded, Ram went up a bit (as it should), and then held pretty much steady.
Expected Results:
It's always worked in the past. it just did it this once. There might be some memory leak with the streaming aspect of Firefox. I had been doing a lot of off-and-on streaming, standing-by the computer, hibernating.
I couldn't get my download manager closed after I had killed the main browser. I had to use Task Manager -> End Process
Comment 1•16 years ago
|
||
Can you create a new profile, and try to reproduce it there? Also, we need some more info, http://quality.mozilla.org/bug-writing-guidelines can help you find out what to give.
Severity: minor → normal
Version: unspecified → 3.5 Branch
Comment 2•16 years ago
|
||
=> incomplete due to no response
However, please comment if you still see this with v3.6, new profile, etc.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•