Closed
Bug 426945
Opened 18 years ago
Closed 17 years ago
FF3 using 20-30% CPU when encountering flash adds
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
INCOMPLETE
People
(Reporter: dewdadew2006, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/2.0.0.12;MEGAUPLOAD 1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/2.0.0.12;MEGAUPLOAD 1.0
New build hogs CPU when encountering flash enabled adds on websites, or sites using adobe flash player(Pandora.com).
Reproducible: Always
Steps to Reproduce:
1. Load any site with adobe flash adds
2. FF3 immediately starts using 20-30% CPU at random
3. Closing tabs does not stop this
Actual Results:
CPU being used 20-30% for no reason.
Expected Results:
Should use aprx 0-5%
This also happens with java enabled sites?
| Reporter | ||
Comment 1•18 years ago
|
||
RAM usage increases as time progresses, much faster than 1.5 or 2.0 did.
Having to close FF3 to free RAM.
Observation: Go to http://www.megabus.com/us/
There's only one flash ad on the page. Cpu is at 25-30%. Cover the add with another window and the cpu goes to idle.
I have the latest plugin Shockwave Flash 9.0 r124
nVidia drivers: 169.21
XP-Pro
related to bug 421643 ?
I'm having the same problems, CPU spikes with flash content. The most reproducible mode is trying to watch a video in Metacafe.com: it's almost impossible, as I get just 5 or 6 fps.
I rolled back to FF2 but with no results. I could check that it doesn't happen in IE7 and doesn't happen with my older (and pretty slower) system (Athlon 2200+ / 1GB DDR / GeForce4 graphics).
My actual system is an Athlon X2 5200+ / 2GB DDR2 / AMD780 chipset / ATI HD3200 onboard graphics.
Comment 5•17 years ago
|
||
This is true for me too. Flash content requires 10% to 15% additional CPU usage per document, so once they add up to 100%, then the browser becomes unresponsive.
This may just be Adobe's fault. They don't seem to have much interest in developing a good product. Flash is a terrible memory and CPU hog. Recently, I reported a bug to Adobe about Flash, and the response I got was was basically a dismissal, telling me that what I described was impossible. Either the person was being very condescending, or English isn't their first language. Either way, my report isn't going to lead to any kind of resolution.
Mind you, Firefox might be able to do something to mitigate the problem. For instance, when no more documents are using Flash, the plugin should be unloaded. It's not, so it continues to use CPU time for nothing. I have to close Firefox and restart to get the CPU usage to go back down.
Comment 6•17 years ago
|
||
I see this behavior (CPU spike) in both FF2 and FF3, however, I can run 12 different Flash swf files simultaneously on one JSP page in IE 6 or 7 and see no noticeable impact on CPU utilization. I don't see how this can be an Adobe issue.
Comment 7•17 years ago
|
||
Joshua do you see the problem when using flash v10?
Comment 8•17 years ago
|
||
=> incomplete due to no response and no working testcases .... http://www.megabus.com/us/ has no flash
this is WFM with ** Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
and Shockwave Flash 10.0 r22
** http://www.mozilla.com/en-US/firefox/all-beta.html
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
Comment 9•17 years ago
|
||
I can confirm that I still see excessive CPU usage with the latest Flash. This is on a Mac. Just because it WFM on Windows doesn't automatically mean the Mac version works as well.
Comment 10•17 years ago
|
||
(In reply to comment #9)
> I can confirm that I still see excessive CPU usage with the latest Flash.
version 3.5 FF?
> This is on a Mac. Just because it WFM on Windows doesn't automatically mean the Mac
> version works as well.
well, the bug was not marked OS=ALL
Comment 11•17 years ago
|
||
I'm using Shiretoko. Is flash handling fundamentally different in 3.5?
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•