PDA

View Full Version : Google Chrome Renderer at 100% CPU When ExtJS 4.1.0 is Idle



iaBrad
7 Jun 2013, 4:19 AM
In Chrome v27.0.1453.110 Mac, we are seeing the Google Chrome Renderer running at 100% (or more) of the CPU, even when our application is idle. There are two timers/loops running. One is in Ext.util.History to track user navigation every 50ms. The other runs a data management function every 30 seconds.


The behavior is the same whether we are using a complicated view with a large grid or a simple view with only a few navigational buttons. The CPU also continues to be taxed, even if JS code execution is paused in the debugger.


When we run the same code in Safari v6.0.5, it uses 0-5% of the CPU.

slemmon
10 Jun 2013, 11:45 AM
I tried loading the History example form 4.2.1 and 4.1.1 in Chrome in Mac and Windows 7 and wasn't seeing anything above 2% CPU.
If you run these examples do you see the same?
http://docs.sencha.com/extjs/4.1.1/extjs-build/examples/history/history.html#main-tabs:tab1:subtab1
http://docs.sencha.com/extjs/4.2.1/extjs-build/examples/history/history.html#main-tabs:tab1:subtab1

Or, do you have a test case you can share that demonstrates the CPU being taxed unnecessarily?