User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1) Gecko/20081007 Firefox/3.1b1 (.NET CLR 3.5.30729) If the firefox is being used and I switch the windows user account to another, firefox on the first user starts to cause a high CPU and memory usage (more than 400 MB occupied and from 50 to 100% of CPU usage). It happens even if nothing has being done before the user switching (no page loading, no downloads...). memory: 2GB CPU: Athlon 64 X2 6000+ OS: Windows Vista x86 SP1 *it has already been occurred on Firefox 3.0.3 Reproducible: Always Steps to Reproduce: 1.Connect to the internet 2.Open firefox 3.View some web pages 4.Switch the windows user account Actual Results: The firefox process on the first user start to use a high amount of memory (more than 400 MB) and increases dramatically the usage of CPU (from 50 to 100% oscillating) on both of the two cores. Expected Results: The firefox process of the first user wasn't doing anything (no page loading, no downloads in progress...), so is expected that firefox behaves like an idle process (low CPU usage). When it occurs and I back to the first user, the issue persists. If I disconnect and reconnect the internet connection, the high CPU usage ceases, even if i return to switch the windows user account.
This is a mass search for bugs which are in the Firefox General component, are UNCO, have not been changed for 500 days and have an unspecified version. Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.
Whiteboard: [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 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.