Closed Bug 554641 Opened 14 years ago Closed 14 years ago

Memory leak

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Version:
3.6 Branch
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: joedlh, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2

Firefox seems to have a memory leak in it, or a cascading loop. When I open it, it's using 2-3% of my CPU load. At some point it simply freezes. When I open Process Explorer, it shows that it's using more than 50%. My plugins are Xmarks, Firebug, FireFTP, NoScript, ImageZoom, Java Console, Web Developer, Microsoft .NET Framework Assistant. Security is AVG.

Reproducible: Always

Steps to Reproduce:
1. Start
2. Wait one hour or so.
3. Freezes.
Actual Results:  
Freezes. Will not close. Must be killed in Task Manager or Process Explorer.

Expected Results:  
Not freeze.
When I start it up again after killing it, it works fine for a while. Then starts to slow down and eventually hang.
Version: unspecified → 3.6 Branch
Stop bothering developers with this minor problem, you are the only one, who has it.
 Kuliks, if the reporter can provide the information we need, we will fix it. No need to be rude
Kuliks, there are several different topics in the support forum which confirm that a lot of users have had hangup and memory problems with 3.6. I, myself, have gone to using Chrome because of it.  Do you ever look at the support forum?  Try looking up this one:

 Why is CPU usage so high in 3.6.2 and 3.6.3 firefox
Ray, unfortunantely, it appears that Kuliks is a spammer. If you are seeing this issue, you can try with a fresh profile and report back to us.
I turned off AVG plugin and the problem went away.
Alright then, please report to AVG.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.