Closed
Bug 146821
Opened 23 years ago
Closed 23 years ago
multiple flash players eat clock cycles, even when not in view
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 132759
People
(Reporter: jd9542, Assigned: rubydoo123)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0rc3)
Gecko/20020523
BuildID: 20020523
I'm not sure if this is with all plugins, but mozilla handles flash much
differently than ie. In mozilla, if you have say, 8 flash players on one page,
it will render those flash players, even when not in view, and even if mozilla
is minimized. In IE6 anyway, the browser does not render flash players that are
not visible, resulting in MUCH less cpu time taken. Never saw this as a problem
before really, but i now frequent a message board where people have flash
signatures, and it slows everything down to a crawl when i use mozilla to browse
these boards. I love mozilla, but i may have to pop open ie for these
particular pages. Please change the way mozilla handles flash.
Reproducible: Always
Steps to Reproduce:
1.go to a page with multiple flash players
2.check mozilla's cpu utlilization
3.scroll down so some of the flash players are not in view
4.check mozilla's cpu utilization again to see that it hasnt changed.
Actual Results: Slows everything down horribly, feels like it crashes mozilla,
but it does not, you just have to wait a really long time before your clicks do
anything.
Expected Results: It would be great if it would not use cpu time on flash
players that are not visible.
wasnt sure if this was proprietary or not, but i noticed mozilla ignores the
<object> tag. This works fine in IE, again, not sure if its some m$ proprietary
bs.
Assignee | ||
Comment 2•23 years ago
|
||
marking as dup
*** This bug has been marked as a duplicate of 132759 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•