Updates:
Summary: High CPU usage on wired.com article.
Status: Untriaged
Cc: [email protected] [email protected]
Comment #6 on issue 20204 by [email protected]: High CPU usage on
wired.com article.
http://code.google.com/p/chromium/issues/detail?id=20204
3986 3.5941 chrome chrome
std::_Deque_iterator<MessageLoop::PendingTask, MessageLoop::PendingTask&,
MessageLoop::PendingTask*>::_Deque_iterator(std::_Deque_iterator<MessageLoop::Pending
Task, MessageLoop::PendingTask&, MessageLoop::PendingTask*> const&)
...
3092 2.7880 chrome chrome
std::__deque_buf_size(unsigned long)
(This is a debug build, so there is probably additional STL checking going
on).
It seems we're spending the time in message loop related code. I'd guess
the page
has a timer firing?
--
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
-~----------~----~----~----~------~----~------~--~---
