Status

()

Firefox
General
--
critical
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: Joseph Dlhopolsky, Unassigned)

Tracking

3.6 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
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.
(Reporter)

Comment 1

8 years ago
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
Please try http://support.mozilla.com/en-US/kb/Safe%20Mode

Comment 3

8 years ago
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

Comment 5

8 years ago
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.
(Reporter)

Comment 7

8 years ago
I turned off AVG plugin and the problem went away.
Alright then, please report to AVG.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.