Description of problem:
gnash in firefox consumes high CPU if swfdec is missing.
In http://www.mbl.is/mm/frettir/ cpu is 100 %.
cpu about 87 %, if the site is open in more than four taps cpu goes uppt 100 % and firefox crashes.
IF swfdec is innstalle then cpu is more resonable.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
open System Monitor
open in firefox How%20software%20patents%20work
reasonable cpu as when swfdec is innstalled.
when swfdec is installed then cpu is much lower.
wait a little time for patents window, if is opened in many windows firefox crashes.
swfdec is a different alternative to gnash, most likely you're getting swfdec when both are installed.
This is also in F10 ( was fully updated ).
I think it's really a general Gnash issue, not related to the distribution at all.
(Also note that installing swfdec isn't a fix for gnash, it's installing a completely different Flash player.)
You should probably file this upstream.
This is an Ogg Theora video, not Flash at all, I don't see how this one is related to Gnash.
On the other hand, http://www.mbl.is/mm/frettir/ does look like a valid testcase.
>You should probably file this upstream.
the one in #4 was in a wrog place
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I can confirm this one for Fedora 12 and gnash 0.9-20090809 (http://www.mbl.is/mm/frettir/ cpu is 100 %.)
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
The same problem in Fedora 14:
The bug in #5 is still open. Also Ubuntu seems to have the same problem:
*** Bug 666672 has been marked as a duplicate of this bug. ***
Please vote for the gnash bug as mentioned in comment 5, see https://savannah.gnu.org/bugs/index.php?26718 and log in to vote.
This may help attract attention to get it fixed.
Is gnash uses much CPU cycles, why does it even display ads? I mean: with flash-plugin from adobe and adblock etc I had no flash ads.
But with an open source solution I do see ads!?
I mean: we don't want to see ads overlaying our video. SO please do not waste cycles at them, or at least make that a documented, configurable option.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
High CPU is due to no hwaccel with the agg renderer which is default. There is XV accel which is badly broken, vaapi which works with intel/nvidia cards AFAIK.
There is nothing we can do about that in downstream fedora, so I am closing this as upstream.
If you can ship a product that can bring a box to grinding halt by just using it in a normal way AND sit back and sigh the 'upstream' mantra, then something is severely missing.
Why can't we signal 'upstream' that there is a problem?!
> vaapi which works with intel/nvidia cards AFAIK.
Last I checked, vaapi was only supported if you build Gnash against FFmpeg instead of GStreamer, which we can't do in Fedora.
> Why can't we signal 'upstream' that there is a problem?!
AFAIK, upstream knows very well that their stuff is slow. But making it fast requires basically rewriting the whole thing.