Hide Forgot
Description of problem: After browsing the website of a local radio station (http://joe.be/home) for a while the laptop's fan started blowing at the maximum rate and the laptop was getting warm. CPU usage was very high: top - 12:13:08 up 1:16, 3 users, load average: 4.62, 3.84, 3.08 Tasks: 153 total, 7 running, 146 sleeping, 0 stopped, 0 zombie Cpu(s): 90.9%us, 7.8%sy, 0.7%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.7%si, 0.0%st Mem: 1019376k total, 964520k used, 54856k free, 6564k buffers Swap: 2097148k total, 194148k used, 1903000k free, 355260k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4442 root 20 0 49408 34m 772 R 59.9 3.4 0:09.87 /usr/bin/applydeltarpm -a x86_64 /var/cache/yum/x86_64/16/updates/deltas/eclipse-platform-3.7.0- 1770 m8ram 20 0 494m 36m 5624 R 45.0 3.7 65:06.33 /usr/bin/gtk-gnash -u http://joe.be/sites/joe.be/themes/joe/flash/billboard.swf -U http://joe.be 1772 m8ram 20 0 489m 29m 5712 R 41.7 2.9 29:16.12 /usr/bin/gtk-gnash -u http://joe.be/sites/joe.be/themes/joe/flash/nowonair.swf -U http://joe.be/ 1773 m8ram 20 0 561m 19m 5364 R 13.6 2.0 9:19.34 /usr/bin/gtk-gnash -u http://www.youtube.com/v/Iyon1TvnLGE?fs=1&hl=nl_NL&color1=0x234900&color2= 1696 m8ram 20 0 1025m 113m 15m S 9.9 11.4 2:41.24 /usr/lib64/firefox/firefox 1091 root 20 0 166m 21m 4624 S 8.9 2.1 2:36.84 /usr/bin/Xorg :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-3jA76n/database -noli 1561 m8ram 20 0 1598m 36m 9148 S 5.6 3.7 2:55.96 /usr/bin/gnome-shell 1769 m8ram 20 0 465m 7972 5252 S 5.3 0.8 3:36.73 /usr/bin/gtk-gnash -u http://joe.be/sites/joe.be/themes/joe/flash/luisterlive.swf -U http://joe. 32505 root 39 19 32320 30m 504 D 2.0 3.1 0:13.38 /usr/sbin/prelink -av -mR -f 1771 m8ram 20 0 465m 7756 4960 S 1.7 0.8 1:09.99 /usr/bin/gtk-gnash -u http://joe.be/sites/joe.be/themes/joe/flash/navigation.swf -U http://joe.b 1914 m8ram 20 0 531m 15m 6528 R 1.3 1.5 0:15.26 /usr/bin/python /usr/bin/terminator 5265 root 20 0 0 0 0 S 1.0 0.0 0:01.13 [kworker/0:2] Version-Release number of selected component (if applicable): [m8ram@latitude ~]$ rpm -qa |grep gnash gnash-plugin-0.8.9-5.fc16.x86_64 gnash-0.8.9-5.fc16.x86_64 [m8ram@latitude ~]$ rpm -qa |grep firefox firefox-7.0.1-3.fc16.x86_64 How reproducible: every time I open this web site and leave it open for a while Steps to Reproduce: open website http://joe.be/home (in firefox) with gnash installed (no flash-plugin installed) Actual results: gnash consumes 80+% CPU Expected results: no noticeable performance impact while surfing
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.