Closed
Bug 1221333
Opened 9 years ago
Closed 3 years ago
100% CPU when playing Flash video in fresh profile; Firefox/Chromium CPU usage graph comparison
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: tyaremco, Unassigned)
Details
Attachments
(1 file)
1.18 KB,
text/plain
|
Details |
My machine is a Lenovo x201s built in 2010. Its graphics adapter is a Mobile Intel(R) 4 Series Express Chipset Family and its CPU is a Intel Core 2 Duo L9400. Firefox cannot play Flash video smoothly on this machine. I played a short flash video in both the recent Chromium and Firefox and logged their CPU usage. The result is almost unbelievable. https://sli.mg/a/5QoQOL - This test is done on a new profiles. - Both browsers have uBlock Origin installed (the issue is unrelated to this extension) - I have tested in the latest nightly with e10s enabled and the result is the same. - Flash hardware acceleration is enabled for both plugins. I have disabled hardware acceleration in the Firefox plugin and the result is the same. - This is not a new regression. Firefox has performed this way for some time. - My graphics chipset drivers are up to date. 1) How can a modern browser integrate so poorly with a well-established plugin as to render the plugin useless on a 5-year-old ultraportable? 2) Even if Mozilla has no intention of supporting my hardware is this the expected level of performance?
Summary: Flash video in Firefox is unusable: Firefox/Chromium CPU graphs → 100% CPU when playing Flash video in fresh profile; Firefox/Chromium CPU usage graph comparison
Workaround: Get a Greasemonkey script that forces the flash object's wmode parameter to "direct". https://greasyfork.org/en/scripts/8914-direct-wmode This bug is well-defined and very detrimental. I can't believe it exists in 2015.
Comment 2•3 years ago
|
||
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•