Chrome hangs completely in bad network conditions
Reported by
vadimkan...@gmail.com,
Mar 2 2017
|
|||||||||||||||||||||||||
Issue descriptionChrome Version : 56.0.2924.87 (Official Build) (64-bit), revision 0e9a9a6f3676ae439b78cd9b3f62b4193c3ac7d5-refs/branch-heads/2924@{#895} URLs (if applicable) : Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: PASS/FAIL (Version) Firefox: PASS/FAIL (Version) IE: PASS/FAIL (Version) What steps will reproduce the problem? (1) Open many tabs (say, facebook.com, but the problem is with all sites). I have a few dozen tabs in several Chrome windows. (2) Increase latency and packet loss (in practice just use bad overloaded Wi-Fi AP) (3) Open a new tab and try to load any URL What is the expected result? UI is responsive, you can read and scroll already loaded tabs, close tabs etc. What happens instead? Whole browser hangs completely, cannot switch tabs (even tab-switch top part becomes blank) or scroll and CPU utilisation rises. Please provide any additional information below. Attach a screenshot if possible. Stack-trace from Process Explorer, captured during a long hang from a most-CPU consuming Chrome renderer process, top thread (I hope it's the hunted UI thread): ntdll.dll!NtWaitForSingleObject+0x14 KERNELBASE.dll!WaitForSingleObjectEx+0x8f chrome_child.dll!ovly_debug_event+0x12a56d chrome_child.dll!ovly_debug_event+0x12bca6 chrome_child.dll!ChromeMain+0x4f9f chrome_child.dll!ChromeMain+0x267471 chrome_child.dll!ChromeMain+0x4b8 chrome_child.dll!ChromeMain+0xb86 chrome_child.dll!ChromeMain+0xab5 chrome_child.dll!ChromeMain+0x119 chrome.exe+0x75ea chrome.exe+0x20d1 chrome.exe!IsSandboxedProcess+0x41fa3 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21 For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Mar 2 2017
Thanks for filing. Probably if the whole browser is hung you want to log what is happening in the browser process, not the renderer process. Thank you for offering to grab a symbolized stack trace :)
,
Mar 7 2017
,
Mar 8 2017
I don't think that trace is useful, unfortunately - WaitForSingleObjectEx is just a thread waiting for an event to happen, so shouldn't be using any CPU time. You sure you got a trace from the right thread?
,
Mar 9 2017
I've installed Chrome's symbols successfully, will try to get a better stack trace. For now waiting for Wi-Fi to get really bad. Basically when 80% of pings were timed-out and the rest were taking 3 seconds was almost guaranteeing a repro. Do you know of a tool for Windows that can emulate such bad network conditions? (preferably some driver to emulate hanging in the Windows kernel)
,
Mar 9 2017
Managed to get a few stack traces from the first thread on the main browser process: ntdll.dll!NtWaitForAlertByThreadId+0x14 ntdll.dll!RtlSleepConditionVariableSRW+0xf5 KERNELBASE.dll!SleepConditionVariableSRW+0x28 chrome.dll!base::ConditionVariable::Wait+0x1d chrome.dll!mojo::edk::Core::WaitManyInternal+0x407 chrome.dll!MojoWaitImpl+0x8f chrome.dll!mojo::SyncHandleRegistry::WatchAllHandles+0x61 chrome.dll!IPC::SyncChannel::WaitForReply+0x204 chrome.dll!IPC::SyncChannel::Send+0x1a7 chrome.dll!gpu::GpuChannelHost::Send+0x4c chrome.dll!gpu::CommandBufferProxyImpl::Send+0x36 chrome.dll!gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange+0x129 chrome.dll!gpu::CommandBufferHelper::WaitForGetOffsetInRange+0x26 chrome.dll!gpu::CommandBufferHelper::Finish+0xa4 chrome.dll!gpu::gles2::GLES2Implementation::WaitForCmd+0x73 chrome.dll!gpu::gles2::GLES2Implementation::FreeEverything+0x23 chrome.dll!gpu::gles2::GLES2Implementation::Flush+0x4c chrome.dll!gpu::gles2::GLES2Implementation::SetAggressivelyFreeResources+0xa4 chrome.dll!cc::ContextCacheController::OnIdle+0x7d chrome.dll!base::internal::Invoker<base::internal::BindState<void (__cdecl cc::ContextCacheController::*)(unsigned int) __ptr64,base::WeakPtr<cc::ContextCacheController>,unsigned int>,void __cdecl(void)>::Run+0x38 chrome.dll!base::debug::TaskAnnotator::RunTask+0x29e chrome.dll!base::MessageLoop::RunTask+0x495 chrome.dll!base::MessageLoop::DeferOrRunPendingTask+0x51 chrome.dll!base::MessageLoop::DoDelayedWork+0x185 chrome.dll!base::MessagePumpForUI::DoRunLoop+0x8b chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21 ntdll.dll!NtWaitForAlertByThreadId+0x14 ntdll.dll!RtlSleepConditionVariableSRW+0xf5 KERNELBASE.dll!SleepConditionVariableSRW+0x28 chrome.dll!base::ConditionVariable::Wait+0x1d chrome.dll!mojo::edk::Core::WaitManyInternal+0x407 chrome.dll!MojoWaitImpl+0x8f chrome.dll!mojo::SyncHandleRegistry::WatchAllHandles+0x61 chrome.dll!IPC::SyncChannel::WaitForReply+0x204 chrome.dll!IPC::SyncChannel::Send+0x1a7 chrome.dll!gpu::GpuChannelHost::Send+0x4c chrome.dll!gpu::CommandBufferProxyImpl::Send+0x36 chrome.dll!gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange+0x129 chrome.dll!gpu::CommandBufferHelper::WaitForGetOffsetInRange+0x26 chrome.dll!gpu::CommandBufferHelper::Finish+0xa4 chrome.dll!gpu::gles2::GLES2Implementation::WaitForCmd+0x73 chrome.dll!gpu::gles2::GLES2Implementation::FreeEverything+0x23 chrome.dll!gpu::gles2::GLES2Implementation::Flush+0x4c chrome.dll!gpu::gles2::GLES2Implementation::SetAggressivelyFreeResources+0xa4 chrome.dll!cc::ContextCacheController::OnIdle+0x7d chrome.dll!base::internal::Invoker<base::internal::BindState<void (__cdecl cc::ContextCacheController::*)(unsigned int) __ptr64,base::WeakPtr<cc::ContextCacheController>,unsigned int>,void __cdecl(void)>::Run+0x38 chrome.dll!base::debug::TaskAnnotator::RunTask+0x29e chrome.dll!base::MessageLoop::RunTask+0x495 chrome.dll!base::MessageLoop::DeferOrRunPendingTask+0x51 chrome.dll!base::MessageLoop::DoDelayedWork+0x185 chrome.dll!base::MessagePumpForUI::DoRunLoop+0x8b chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21 ntdll.dll!NtWaitForAlertByThreadId+0x14 ntdll.dll!RtlSleepConditionVariableSRW+0xf5 KERNELBASE.dll!SleepConditionVariableSRW+0x28 chrome.dll!base::ConditionVariable::Wait+0x1d chrome.dll!mojo::edk::Core::WaitManyInternal+0x407 chrome.dll!MojoWaitImpl+0x8f chrome.dll!mojo::SyncHandleRegistry::WatchAllHandles+0x61 chrome.dll!IPC::SyncChannel::WaitForReply+0x204 chrome.dll!IPC::SyncChannel::Send+0x1a7 chrome.dll!gpu::GpuChannelHost::Send+0x4c chrome.dll!gpu::CommandBufferProxyImpl::Send+0x36 chrome.dll!gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange+0x129 chrome.dll!gpu::CommandBufferHelper::WaitForGetOffsetInRange+0x26 chrome.dll!gpu::CommandBufferHelper::Finish+0xa4 chrome.dll!gpu::gles2::GLES2Implementation::WaitForCmd+0x73 chrome.dll!gpu::gles2::GLES2Implementation::FreeEverything+0x23 chrome.dll!gpu::gles2::GLES2Implementation::Flush+0x4c chrome.dll!gpu::gles2::GLES2Implementation::SetAggressivelyFreeResources+0xa4 chrome.dll!cc::ContextCacheController::OnIdle+0x7d chrome.dll!base::internal::Invoker<base::internal::BindState<void (__cdecl cc::ContextCacheController::*)(unsigned int) __ptr64,base::WeakPtr<cc::ContextCacheController>,unsigned int>,void __cdecl(void)>::Run+0x38 chrome.dll!base::debug::TaskAnnotator::RunTask+0x29e chrome.dll!base::MessageLoop::RunTask+0x495 chrome.dll!base::MessageLoop::DeferOrRunPendingTask+0x51 chrome.dll!base::MessageLoop::DoDelayedWork+0x185 chrome.dll!base::MessagePumpForUI::DoRunLoop+0x8b chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21 ntdll.dll!NtWaitForAlertByThreadId+0x14 ntdll.dll!RtlSleepConditionVariableSRW+0xf5 KERNELBASE.dll!SleepConditionVariableSRW+0x28 chrome.dll!base::ConditionVariable::Wait+0x1d chrome.dll!mojo::edk::Core::WaitManyInternal+0x407 chrome.dll!MojoWaitImpl+0x8f chrome.dll!mojo::SyncHandleRegistry::WatchAllHandles+0x61 chrome.dll!IPC::SyncChannel::WaitForReply+0x204 chrome.dll!IPC::SyncChannel::Send+0x1a7 chrome.dll!gpu::GpuChannelHost::Send+0x4c chrome.dll!gpu::CommandBufferProxyImpl::Send+0x36 chrome.dll!gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange+0x129 chrome.dll!gpu::CommandBufferHelper::WaitForGetOffsetInRange+0x26 chrome.dll!gpu::CommandBufferHelper::Finish+0xa4 chrome.dll!gpu::gles2::GLES2Implementation::WaitForCmd+0x73 chrome.dll!gpu::gles2::GLES2Implementation::FreeEverything+0x23 chrome.dll!gpu::gles2::GLES2Implementation::Flush+0x4c chrome.dll!gpu::gles2::GLES2Implementation::SetAggressivelyFreeResources+0xa4 chrome.dll!cc::ContextCacheController::OnIdle+0x7d chrome.dll!base::internal::Invoker<base::internal::BindState<void (__cdecl cc::ContextCacheController::*)(unsigned int) __ptr64,base::WeakPtr<cc::ContextCacheController>,unsigned int>,void __cdecl(void)>::Run+0x38 chrome.dll!base::debug::TaskAnnotator::RunTask+0x29e chrome.dll!base::MessageLoop::RunTask+0x495 chrome.dll!base::MessageLoop::DeferOrRunPendingTask+0x51 chrome.dll!base::MessageLoop::DoDelayedWork+0x185 chrome.dll!base::MessagePumpForUI::DoRunLoop+0x8b chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21 win32u.dll!NtUserPeekMessage+0x14 USER32.dll!PeekMessageW+0xfe chrome.dll!base::MessagePumpForUI::WaitForWork+0x98 chrome.dll!base::MessagePumpForUI::DoRunLoop+0xda chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21
,
Mar 9 2017
Looks like the UI thread is doing nothing. All the others are GPU threads waiting on sync IPCs. No idea if that's expected.
,
Mar 9 2017
I restored internet connection, Chrome unhung. A healthy UI thread looks like below. Could it be that the UI thread is actually blocked by waiting on GPU threads? and thus not redrawing menus, processing clicks etc. ntdll.dll!NtWaitForMultipleObjects+0x14 KERNELBASE.dll!WaitForMultipleObjectsEx+0xef USER32.dll!MsgWaitForMultipleObjectsEx+0x15b chrome.dll!base::MessagePumpForUI::WaitForWork+0x4a chrome.dll!base::MessagePumpForUI::DoRunLoop+0xda chrome.dll!base::MessagePumpWin::Run+0x54 chrome.dll!base::RunLoop::Run+0x103 chrome.dll!ChromeBrowserMainParts::MainMessageLoopRun+0xef chrome.dll!content::BrowserMainRunnerImpl::Run+0x71 chrome.dll!content::BrowserMain+0xef chrome.dll!content::ContentMainRunnerImpl::Run+0x1ff chrome.dll!ChromeMain+0x1a1 chrome.exe!MainDllLoader::Launch+0x38e chrome.exe!wWinMain+0x291 chrome.exe!__scrt_common_main_seh+0x117 KERNEL32.DLL!BaseThreadInitThunk+0x14 ntdll.dll!RtlUserThreadStart+0x21
,
Mar 9 2017
Do you think you might be able to provide some extra detail about what is happening with the network? Please see the following instructions: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Mar 10 2017
@mmenke All these stack traces are from the main UI thread. I just took a few samples. @ckrasic I'll try to collect the net stats.
,
Mar 10 2017
Thank you for providing more feedback. Adding requester "ckrasic@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 10 2017
Per comment #10, still waiting for network log, thus re-adding Needs-Feedback label.
,
Mar 21 2017
Thank you for providing more feedback. Adding requester "bnc@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 23 2017
I do see lots of TCP socket connect jobs and associated hung URL_REQUESTS, HTTP_STREAM_JOBS, etc. But other than the net sucking, I don't see anything obviously wrong with net-internals. I don't think that this is a Networking bug, though I could be wrong.
,
Mar 31 2017
I moved out of the sluggish internet hotel, so won't be providing a screenshot till the next conference. Hope someone could look at why network sucking causes full UI stops and endless waits of UI thread.
,
Apr 13 2017
cc'ing some GPU folks: looks like the ubercompositor has multiple threads blocked while attempting to AggressivelyFreeResources simultaneously. Is that normal? Perhaps the GPU process is hung or died and the browser doesn't know?
,
Apr 13 2017
Yeah, could the reporter get a backtrace from the GPU process when the browser's hung? Also attach a copy of about:gpu here, please. It's weird that that bad network conditions could cause the GPU process to misbehave.
,
Apr 17 2017
This may be unrelated, but previously when we had "the big Net leak", it manifested as the GPU IPCs getting blocked, due to browser's IO thread being blocked on Net tasks.
,
Apr 18 2017
If you know a WinDbg command sequence (I've never ued WinDbg before) or another way to dump all stacktraces of all threads of all processes, I can try it. Otherwise it's hard to find the right process, I'm running many windows and thus have many dozen Chrome processes. Attaching about:gpu dump. If you know of a way to emulate network hiccups on driver level, I can try it too.
,
Apr 18 2017
Re comment #20: One approach is to use Process Explorer to save a minidump for the process(s) in question. Get it here: https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx When you launch process explorer you will see a tree view of the processes. Right click on the one of interest, then pick "Create Dump -> Create Minidump" To figure out which one is the GPU process, you can use Chromes "Task Manager" (Chrome's menu -> More tools -> Task manager); or shift-esc shortcut. This will show the process ID for GPU. Once you have the .dmp file (minidump) you can attach it directly to this bug (it may contain some information such as your username though). Alternately if you don't feel comfortable doing that, you can open the .dmp in WinDBG and list all thread callstacks by running command "~*k" (no quotes)
,
Apr 18 2017
,
Apr 20 2017
(I don't see this could be helped by Blink>Loader fixes either, so removing the component-- feel free to re-add otherwise.)
,
Apr 28 2017
re comment #20 could you try what comment #21 suggests?
,
Apr 28 2017
Since I'm back home where I have good network connection, I haven't had the occasion to dump the hung Chrome. I'll try to use Clumsy (http://jagt.github.io/clumsy/) for imitating bad network at driver level, when I have time.
,
Apr 28 2017
Thank you for providing more feedback. Adding requester "weiliangc@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 28 2017
Thanks.
,
May 3 2017
Having a stack trace of the IO thread would be helpful. I have seen a bunch of instances where the IO thread was stuck doing networking things (or other) and that blocked communication with the GPU process. See e.g. crbug.com/661306, crbug.com/703342, crbug.com/667820
,
May 19 2017
I tried hard to make it fail with Clumsy. It seemed for a moment it worked and I took a mini-dump of the main browser process. Hope it's useful. Since it was hard to make, the failures emulated by Clumsy are apparently not identical to slow and faulty wifi networks.
,
May 19 2017
Thank you for providing more feedback. Adding requester "weiliangc@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 19 2017
eroman@, can you take a look at the dump in #29 or reassign to someone else who could do that?
,
May 22 2017
The UI thread in the attached dump is busy drawing in response to some extension code. Could be luck of when you sampled the process, or it could point to the culprit being extensions. Do you reproduce the slowness if you disable your Chrome extensions? (Attached the symbolized thread callstacks from comment #29's minidump) Child-SP RetAddr Call Site 000000e1`a21faa58 00007ffd`b82ff321 chrome_7ffdb71a0000!display::Display::Display+0x5 [c:\b\c\b\win64_pgo\src\ui\display\display.cc @ 95] 000000e1`a21faa60 00007ffd`b82ffb3e chrome_7ffdb71a0000!display::win::ScreenWin::ScreenToDIPRect+0x8d [c:\b\c\b\win64_pgo\src\ui\display\win\screen_win.cc @ 256] 000000e1`a21fadc0 00007ffd`b91beeab chrome_7ffdb71a0000!display::win::ScreenWin::ScreenToDIPRectInWindow+0x2e [c:\b\c\b\win64_pgo\src\ui\display\win\screen_win.cc @ 437] 000000e1`a21fadf0 00007ffd`b91bef08 chrome_7ffdb71a0000!wm::DefaultScreenPositionClient::GetOriginInScreen+0x53 [c:\b\c\b\win64_pgo\src\ui\wm\core\default_screen_position_client.cc @ 26] 000000e1`a21fae40 00007ffd`b85631a6 chrome_7ffdb71a0000!wm::DefaultScreenPositionClient::ConvertPointToScreen+0x38 [c:\b\c\b\win64_pgo\src\ui\wm\core\default_screen_position_client.cc @ 35] 000000e1`a21fae70 00007ffd`b785bcd7 chrome_7ffdb71a0000!aura::Window::GetBoundsInScreen+0x4e [c:\b\c\b\win64_pgo\src\ui\aura\window.cc @ 251] 000000e1`a21faea0 00007ffd`b784e9df chrome_7ffdb71a0000!content::WebContentsViewAura::GetContainerBounds+0x17 [c:\b\c\b\win64_pgo\src\content\browser\web_contents\web_contents_view_aura.cc @ 742] 000000e1`a21faee0 00007ffd`b88fbbec chrome_7ffdb71a0000!content::WebContentsImpl::GetContainerBounds+0x1f [c:\b\c\b\win64_pgo\src\content\browser\web_contents\web_contents_impl.cc @ 2857] 000000e1`a21faf10 00007ffd`b88fb7ad chrome_7ffdb71a0000!extensions::ExtensionTabUtil::CreateTabObject+0x2f8 [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\extension_tab_util.cc @ 407] 000000e1`a21faf90 00007ffd`b88fb86c chrome_7ffdb71a0000!extensions::ExtensionTabUtil::CreateTabObject+0x79 [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\extension_tab_util.cc @ 357] 000000e1`a21fafd0 00007ffd`b929789e chrome_7ffdb71a0000!extensions::ExtensionTabUtil::CreateTabList+0x84 [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\extension_tab_util.cc @ 367] 000000e1`a21fb030 00007ffd`b9234789 chrome_7ffdb71a0000!BrowserExtensionWindowController::CreateWindowValueWithTabs+0x4e [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\browser_extension_window_controller.cc @ 49] 000000e1`a21fb070 00007ffd`b78f9d1d chrome_7ffdb71a0000!extensions::WindowsGetAllFunction::Run+0xe9 [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\api\tabs\tabs_api.cc @ 361] 000000e1`a21fb0e0 00007ffd`b78fc00d chrome_7ffdb71a0000!ExtensionFunction::RunWithValidation+0xdd [c:\b\c\b\win64_pgo\src\extensions\browser\extension_function.cc @ 457] 000000e1`a21fb150 00007ffd`b78fba59 chrome_7ffdb71a0000!extensions::ExtensionFunctionDispatcher::DispatchWithCallbackInternal+0x365 [c:\b\c\b\win64_pgo\src\extensions\browser\extension_function_dispatcher.cc @ 486] 000000e1`a21fb350 00007ffd`b791631a chrome_7ffdb71a0000!extensions::ExtensionFunctionDispatcher::Dispatch+0x28d [c:\b\c\b\win64_pgo\src\extensions\browser\extension_function_dispatcher.cc @ 382] (Inline Function) --------`-------- chrome_7ffdb71a0000!IPC::DispatchToMethodImpl+0x21 [c:\b\c\b\win64_pgo\src\ipc\ipc_message_templates.h @ 40] (Inline Function) --------`-------- chrome_7ffdb71a0000!IPC::DispatchToMethod+0x26 [c:\b\c\b\win64_pgo\src\ipc\ipc_message_templates.h @ 51] 000000e1`a21fb460 00007ffd`b7915c21 chrome_7ffdb71a0000!IPC::MessageT<ExtensionHostMsg_Request_Meta,std::tuple<ExtensionHostMsg_Request_Params>,void>::Dispatch<extensions::ExtensionWebContentsObserver,extensions::ExtensionWebContentsObserver,content::RenderFrameHost,void (__cdecl extensions::ExtensionWebContentsObserver::*)(content::RenderFrameHost * __ptr64,ExtensionHostMsg_Request_Params const & __ptr64) __ptr64>+0x15e [c:\b\c\b\win64_pgo\src\ipc\ipc_message_templates.h @ 121] 000000e1`a21fb670 00007ffd`b8901744 chrome_7ffdb71a0000!extensions::ExtensionWebContentsObserver::OnMessageReceived+0xd1 [c:\b\c\b\win64_pgo\src\extensions\browser\extension_web_contents_observer.cc @ 170] 000000e1`a21fb780 00007ffd`b78477ea chrome_7ffdb71a0000!extensions::ChromeExtensionWebContentsObserver::OnMessageReceived+0x34 [c:\b\c\b\win64_pgo\src\chrome\browser\extensions\chrome_extension_web_contents_observer.cc @ 92] 000000e1`a21fb890 00007ffd`b7642815 chrome_7ffdb71a0000!content::WebContentsImpl::OnMessageReceived+0x7a [c:\b\c\b\win64_pgo\src\content\browser\web_contents\web_contents_impl.cc @ 744] 000000e1`a21fc810 00007ffd`b777e19a chrome_7ffdb71a0000!content::RenderFrameHostImpl::OnMessageReceived+0x115 [c:\b\c\b\win64_pgo\src\content\browser\frame_host\render_frame_host_impl.cc @ 668] 000000e1`a21fe840 00007ffd`b7f78c48 chrome_7ffdb71a0000!content::RenderProcessHostImpl::OnMessageReceived+0x55a [c:\b\c\b\win64_pgo\src\content\browser\renderer_host\render_process_host_impl.cc @ 2081] 000000e1`a21fec90 00007ffd`b73873e0 chrome_7ffdb71a0000!IPC::ChannelProxy::Context::OnDispatchMessage+0x28 [c:\b\c\b\win64_pgo\src\ipc\ipc_channel_proxy.cc @ 330] 000000e1`a21fecc0 00007ffd`b7c062c3 chrome_7ffdb71a0000!base::internal::RunMixin<base::Callback<void __cdecl(void),0,0> >::Run+0x24 [c:\b\c\b\win64_pgo\src\base\callback.h @ 68] 000000e1`a21fecf0 00007ffd`b7bb5346 chrome_7ffdb71a0000!base::debug::TaskAnnotator::RunTask+0x183 [c:\b\c\b\win64_pgo\src\base\debug\task_annotator.cc @ 61] 000000e1`a21fee80 00007ffd`b7bb5efa chrome_7ffdb71a0000!base::MessageLoop::RunTask+0x1f6 [c:\b\c\b\win64_pgo\src\base\message_loop\message_loop.cc @ 424] (Inline Function) --------`-------- chrome_7ffdb71a0000!base::MessageLoop::DeferOrRunPendingTask+0x56 [c:\b\c\b\win64_pgo\src\base\message_loop\message_loop.cc @ 434] 000000e1`a21fefe0 00007ffd`b7c06831 chrome_7ffdb71a0000!base::MessageLoop::DoWork+0x48a [c:\b\c\b\win64_pgo\src\base\message_loop\message_loop.cc @ 527] 000000e1`a21ff1e0 00007ffd`b7c06484 chrome_7ffdb71a0000!base::MessagePumpForUI::DoRunLoop+0x71 [c:\b\c\b\win64_pgo\src\base\message_loop\message_pump_win.cc @ 174] 000000e1`a21ff250 00007ffd`b7bdd2e0 chrome_7ffdb71a0000!base::MessagePumpWin::Run+0x54 [c:\b\c\b\win64_pgo\src\base\message_loop\message_pump_win.cc @ 58] (Inline Function) --------`-------- chrome_7ffdb71a0000!base::RunLoop::Run+0xc0 [c:\b\c\b\win64_pgo\src\base\message_loop\message_loop.cc @ 387] 000000e1`a21ff2a0 00007ffd`b7ae1d98 chrome_7ffdb71a0000!base::RunLoop::Run+0xc0 [c:\b\c\b\win64_pgo\src\base\run_loop.cc @ 38] 000000e1`a21ff350 00007ffd`b757c44c chrome_7ffdb71a0000!ChromeBrowserMainParts::MainMessageLoopRun+0x138 [c:\b\c\b\win64_pgo\src\chrome\browser\chrome_browser_main.cc @ 2009] (Inline Function) --------`-------- chrome_7ffdb71a0000!content::BrowserMainRunnerImpl::Run+0x6c [c:\b\c\b\win64_pgo\src\content\browser\browser_main_loop.cc @ 1183] 000000e1`a21ff3d0 00007ffd`b7574669 chrome_7ffdb71a0000!content::BrowserMainRunnerImpl::Run+0x6c [c:\b\c\b\win64_pgo\src\content\browser\browser_main_runner.cc @ 140] 000000e1`a21ff420 00007ffd`b7a933e3 chrome_7ffdb71a0000!content::BrowserMain+0x169 [c:\b\c\b\win64_pgo\src\content\browser\browser_main.cc @ 46] (Inline Function) --------`-------- chrome_7ffdb71a0000!content::RunNamedProcessTypeMain+0x157 [c:\b\c\b\win64_pgo\src\content\app\content_main_runner.cc @ 491] 000000e1`a21ff4b0 00007ffd`b7263c4c chrome_7ffdb71a0000!content::ContentMainRunnerImpl::Run+0x243 [c:\b\c\b\win64_pgo\src\content\app\content_main_runner.cc @ 836] (Inline Function) --------`-------- chrome_7ffdb71a0000!ChromeMain+0x19c [c:\b\c\b\win64_pgo\src\content\app\content_main.cc @ 20] 000000e1`a21ff660 00007ff6`a51475bc chrome_7ffdb71a0000!ChromeMain+0x19c [c:\b\c\b\win64_pgo\src\chrome\app\chrome_main.cc @ 121] 000000e1`a21ff6f0 00007ff6`a514267b chrome!MainDllLoader::Launch+0x3a4 [c:\b\c\b\win64_pgo\src\chrome\app\main_dll_loader_win.cc @ 203] 000000e1`a21ff820 00007ff6`a51d5e13 chrome!wWinMain+0x2b7 [c:\b\c\b\win64_pgo\src\chrome\app\chrome_exe_main_win.cc @ 285] (Inline Function) --------`-------- chrome!invoke_main+0x21 [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 113] 000000e1`a21ffa20 00007ffd`dee78364 chrome!__scrt_common_main_seh+0x117 [f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl @ 253] 000000e1`a21ffa60 00007ffd`e0e070d1 kernel32!BaseThreadInitThunk+0x14 000000e1`a21ffa90 00000000`00000000 ntdll!RtlUserThreadStart+0x21
,
May 26 2017
,
Jun 7 2017
With this mini-dump it may be the extension to blame, I observerd the original issue before I installed the extension. Since I couldn't repro the issue with Clumsy, I will put a mini-dump here once I again have a problem with bad Wi-Fi at some hotel.
,
Jun 8 2017
,
Jun 11 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 29 2018
I'm going to close this issue since we don't have a repro and without a dump from the GPU process, there is nothing actionable we can do to diagnose what caused it to be unresponsive. vadimkantorov@, please feel free to re-open it if you have a repro. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vadimkan...@gmail.com
, Mar 2 2017