Created attachment 586880 [details] Trace I saw on the console Description of problem: Microsoft Office Live Meeting applet pushes CPU load to 100% Version-Release number of selected component (if applicable): icedtea-web-1.2-1.fc16.x86_64 How reproducible: Seemingly not with the test applet, but it burned through almost all of my battery on an actual meeting I had to attend :( Steps to Reproduce: 1. Go to live meeting applet (happened as an attendee) using Firefox Nightly (Linux x86_64) Actual results: Watch CPU go to 100% and above Expected results: Reasonable CPU usage Additional info: Test applet doesn't seem to reproduce problem: https://www125.livemeeting.com/cc/test2007/webJoin Maybe it requires changing content in the meeting?
Given that it does not happen with the test applet, it is very likely that this is an issue with the applet :( Unfortunately there is not much to go by in the attachment (that trace is fine to ignore). If you happen to be in a meeting in the future, can you please try the following: 1. ps aux | grep PluginMain 2. Note the pid and then run: 2a. jstack -l <pid> 2b. jstack -l -m <pid> And attach the outputs? That will tell which threads and active and I'll have a better of idea if something that shouldn't be active is active.
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.