Comment #17 on issue 12189 by darthandroid: Renderer freezes http://code.google.com/p/chromium/issues/detail?id=12189
Please ignore the stacktrace in my previous comment; it is completely inaccurate due to the lack of symbols I have a development environment set up and can build chrome successfully, however profiling via visual studio's tools has been unproductive - instrumentation profiling causes the renderer executables not to spawn correctly and sample profiling bluescreens my computer due to KB958842 (which won't install for some reason). A more accurate stack trace for some arbitrary point in time while the browser is frozen follows: thread chrome.exe!wWinMainCRTStartup 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!base::MessagePumpForUI::WaitForWork+0x51 11 chrome.dll!base::MessagePumpForUI::DoRunLoop+0x144 12 chrome.dll!base::MessagePumpWin::RunWithDispatcher+0x82 13 chrome.dll!MessageLoop::RunInternal+0xdf 14 chrome.dll!MessageLoop::RunHandler+0x2b 15 chrome.dll!MessageLoopForUI::Run+0x49 16 chrome.dll!`anonymous namespace'::RunUIMessageLoop+0x2e 17 chrome.dll!BrowserMain+0x2489 18 chrome.dll!ChromeMain+0x81b 19 chrome.exe!MainDllLoader::Launch+0x114 20 chrome.exe!wWinMain+0xb2 21 chrome.exe!__tmainCRTStartup+0x165 22 chrome.exe!wWinMainCRTStartup+0xf 23 kernel32.dll!BaseThreadInitThunk+0x12 24 ntdll.dll!RtlInitializeExceptionChain+0x63 25 ntdll.dll!RtlInitializeExceptionChain+0x36 While the chrome-specific symbols are different since I have symbols this time, the beginning and ending stack frames for non-chrome code. Examining the thread while not frozen leads to a wide array of stack traces for things such as repainting the window , but while frozen the stacktrace for this thread is always the same. I can't offer any insight as far as reproducing the problem, but if any of the developers have any suggestions on what to examine/look for I can certainly help with debugging. In the meantime I'll work on getting profiling working so I can see exactly where the time is going during the freezes. -- 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
