Firefox process running at 50% when running Folding@Home

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
11 years ago
8 years ago

People

(Reporter: tim.swett, Unassigned)

Tracking

2.0 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-05-01])

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007110505 Minefield/3.0a9pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007110505 Minefield/3.0a9pre

When running Folding@home at the same time I run Firefox (2.0.0.9 or latest build of 3), Firefox process starts running up to 50% (Folding@Home uses 50% processor power.) When I pause the work on Folding@Home, the processor usage of Firefox goes down to a moderate 5% or so, fluctuating between 0%-5%/10%.  

Reproducible: Always

Steps to Reproduce:
1.Run Folding@Home from Stanford University
2.Open Firefox to a webpage (i.e. www.google.com/ig or www.digg.com)
3.Look at CPU Usage of both applications (Folding@home should be 50%, Firefox will fluctuate between 40%-50%
4.Pause work on Folding@Home
5.Look at CPU Usage of both applications
Actual Results:  
After pausing work from folding@home, Firefox's CPU usage dropped significantly.

Expected Results:  
See above.

about:buildconfig

Build platform
target
i686-pc-mingw32

Build tools
Compiler 	Version 	Compiler flags
cl 	14.00.50727 	-TC -nologo -W3 -Gy -Fd$(PDBFILE)
cl 	14.00.50727 	-GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fd$(PDBFILE)

Configure arguments
--enable-application=browser --enable-update-channel=nightly --enable-optimize --disable-debug --disable-tests --enable-update-packaging

Updated

8 years ago
Version: unspecified → 2.0 Branch
Does this happen with firefox 4 or later with a fresh profile?
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-05-01]
This was filed in the incorrect component anyways so resolving -> incomplete. If this is still happening please reopen and move to Firefox -> General for further triage
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.