Comment #15 on issue 12666 by [email protected]: Continual RAM growth and
10% CPU usage on page.
http://code.google.com/p/chromium/issues/detail?id=12666
This is from /default/js/newsticker.js on that website:
function TICKER_tick() {
if(!TICKER_PAUSED) document.getElementById("TICKER").scrollLeft +=
TICKER_SPEED * (TICKER_RIGHTTOLEFT ? -1 : 1);
if(TICKER_RIGHTTOLEFT && document.getElementById("TICKER").scrollLeft
<=
0) document.getElementById("TICKER").scrollLeft =
document.getElementById("TICKER").scrollWidth -
document.getElementById("TICKER").offsetWidth;
if(!TICKER_RIGHTTOLEFT && document.getElementById("TICKER").scrollLeft
>=
document.getElementById("TICKER").scrollWidth -
document.getElementById("TICKER").offsetWidth)
document.getElementById("TICKER").scrollLeft = 0;
window.setTimeout("TICKER_tick()", 30);
}
so it's not at all surprising that Chrome would continue to use CPU
indefinitely - the setTimeout() will keep firing every 30ms. Neutering the
timer tick (by executing TIMER_tick =
function () {} in the inspector console) does drop the CPU use of this tab
down to zero.
We still should not be leaking any memory in Chrome and should not be using
any more CPU than other browsers so I'll keep digging.
--
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
-~----------~----~----~----~------~----~------~--~---
