Comment #12 on issue 6983 by [email protected]: 100% CPU usage in build 2.0.158.0 http://code.google.com/p/chromium/issues/detail?id=6983
Anyone who is having this problem, please try an experiment. Get Process Explorer from Sysinternals/Microsoft if you don’t already have it: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Run it and double-click on the main Chrome.exe in the tree. Click the CPU header to sort the entries by CPU usage. Then use Chrome a bit and open some tabs, etc. to get it to spike the CPU. Look at the Chrome.exe Properties dialog of ProcExp to see what function bubbles to the top of the list under Start Address. Tell me what module/function are using the most CPU. In my case, other than chrome.dll!ChromeMain, it is usually ntdll.dll!RtlPcToFileHeader that sucks the most CPU (and not just in Chrome, but in Explorer too, which points to some other problem). -- 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 -~----------~----~----~----~------~----~------~--~---
