Comment #8 on issue 22948 by [email protected]: web pages eating lots of CPU http://code.google.com/p/chromium/issues/detail?id=22948
A story on nytimes.com was spinning my CPU at 50%. Here was the stack: chrome_1c30000!WTF::highResUpTime+0x7d chrome_1c30000!WTF::currentTime+0x4b chrome_1c30000!WebCore::ThreadTimers::sharedTimerFiredInternal+0x1f chrome_1c30000!WebCore::ThreadTimers::sharedTimerFired+0xe chrome_1c30000!MessageLoop::RunTask+0x1e chrome_1c30000!MessageLoop::DeferOrRunPendingTask+0x2b chrome_1c30000!MessageLoop::DoWork+0x6e chrome_1c30000!base::MessagePumpDefault::Run+0xb9 chrome_1c30000!MessageLoop::RunInternal+0x31 chrome_1c30000!MessageLoop::RunHandler+0x4f chrome_1c30000!MessageLoop::Run+0x15 chrome_1c30000!RendererMain+0x2ad chrome_1c30000!ChromeMain+0x52a chrome!google_update::GoogleUpdateClient::Launch+0x175 chrome!wWinMain+0x2bf chrome!__tmainCRTStartup+0x176 WARNING: Stack unwind information not available. Following frames may be wrong. kernel32!RegisterWaitForInputIdle+0x49 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
