Memory leak / CPU usage high with 3.0.10 on Vista 32

RESOLVED INCOMPLETE

Status

()

Firefox
General
--
major
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: fbonds@gmail.com, Unassigned)

Tracking

({perf})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [closeme 2010-05-10])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

Firefox with tabbed browsing (2-4tabs) on static sites without active content has memory footprint over 225K.  Starts off around 90K, but rapidly doubles/triples and then never comes back down.  CPU while generally close to idle, frequently hits 50%.  Text input, link selection, tab/menu selection frequently slow to point of nearly unusable.

Add-Ons enabled: AdBlock Plus & WOT

No 3rd party toolbars

No themes

Problem has been occurring consistently since .0.10 update.

Reproducible: Always

Steps to Reproduce:
1.  Run and observe under normal usage.
2.
3.
Actual Results:  
Memory footprint larger than seems reasonable given activity
CPU spikes
Poor response times to mouse/keyboard input

Expected Results:  
Reasonable/consistently low memory usuage
No CPU spikes
Realtime click / text input response

Comment 1

8 years ago
do you see this also with Firefox 3.6 started in safe mode?
 http://support.mozilla.com/kb/Safe+Mode

If so, please narrow down to a specific (set of) web page.
Keywords: perf
Whiteboard: [closeme 2010-05-10]
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.