Comment #16 on issue 12189 by darthandroid: Renderer freezes
http://code.google.com/p/chromium/issues/detail?id=12189

I just tried the latest build according to the link posted in comment #13 -  
Fresh
profile stilled showed the problems. Global CPU usage stayed below a single  
core on
my machine, and chrome usage (according to the chrome task manager) was  
1-2% for the
browser and 0 for all tabs while it was frozen.

I ran the browser with --single-process and watched the list of threads  
whenever the
browser froze - each time one thread that otherwise sat at 0 clock cycles  
would jump
to using the most by a factor of 100 and then drop back to 0 just as the  
browser unfroze:

thread chrome.exe!SetActiveURL+0c2a8d6
0  wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
1  wow64cpu.dll!TurboDispatchJumpAddressEnd+0xe3
2  wow64.dll!Wow64SystemServiceEx+0x1ce
3  wow64.dll!Wow64LdrpInitialize+0x429
4  ntdll.dll!RtlResetRtlTranslations+0x1b08
5  ntdll.dll!RtlResetRtlTranslations+0xc63
6  ntdll.dll!LdrInitializeThunk+0xe
7  ntdll.dll!NtWaitForMultipleObjects+0x15
8  kernel32.dll!WaitForMultipleObjectsEx+0x8e
9  USER32.dll!MsgWaitForMultipleObjectsEx+0xfa
10 chrome.dll!ChromeMain+0x3a1387
11 chrome.dll!ChromeMain+0x3a16fd
12 chrome.dll!ChromeMain+0x3a08c2
13 chrome.dll!ChromeMain+0x37d5bf
14 chrome.dll!ChromeMain+0x37e247
15 chrome.dll!ChromeMain+0x1858f
16 chrome.dll!ChromeMain+0x1a5f4
17 chrome.dll!ChromeMain+0x819
18 chrome.exe!SetActiveURL+0x110d
19 chrome.exe!SetActiveURL+0x1540
20 chrome.exe!SetActiveURL+0x2a86d
21 kernel32.dll!BaseThreadInitThunk+0x12
22 ntdll.dll!RtlInitializeExceptionChain+0x63
23 ntdll.dll!RtlInitializeExceptionChain+0x36

This stack trace was grabbed via process explorer while the renderer was  
hung, and
was the same thread each time, regardless of active tab or if tabs had been  
closed. I
know it doesn't give a full picture of the browser's state, but it seems  
the most
suspect.

--
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

Reply via email to