UI freeze on lock screen followed by browser crash with signature gpu::GpuChannelHost::Send |
|||||||
Issue descriptionGoogle Chrome 66.0.3344.0 (Official Build) dev (64-bit) Revision 0 Platform 10409.0.0 (Official Build) dev-channel caroline Magic Signature: gpu::GpuChannelHost::Send Stack trace: 0x00007fbff1de01ff (libpthread-2.23.so + 0x0000d1ff ) pthread_cond_wait 0x00005bbeedeb5dc4 (chrome -condition_variable_posix.cc:71 ) base::ConditionVariable::Wait() 0x00005bbeebe36508 (chrome -waitable_event_posix.cc:223 ) base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) 0x00005bbeedeb625b (chrome -waitable_event_posix.cc:154 ) base::WaitableEvent::Wait() 0x00005bbeec3e2010 (chrome -gpu_channel_host.cc:83 ) gpu::GpuChannelHost::Send(IPC::Message*) 0x00005bbeec3df9be (chrome -command_buffer_proxy_impl.cc:715 ) gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange(unsigned int, int, int) 0x00005bbeec1a2d4c (chrome -cmd_buffer_helper.cc:164 ) gpu::CommandBufferHelper::Finish() 0x00005bbeef1d84ff (chrome -gles2_implementation.cc:1486 ) gpu::gles2::GLES2Implementation::FinishHelper() 0x00005bbeef166bdf (chrome -layer_tree_resource_provider.cc:131 ) cc::LayerTreeResourceProvider::~LayerTreeResourceProvider() 0x00005bbeef166c6d (chrome -layer_tree_resource_provider.cc:121 ) cc::LayerTreeResourceProvider::~LayerTreeResourceProvider() 0x00005bbeef132646 (chrome -memory:2399 ) cc::LayerTreeHostImpl::ReleaseLayerTreeFrameSink() 0x00005bbeef1a8845 (chrome -single_thread_proxy.cc:294 ) cc::SingleThreadProxy::Stop() 0x00005bbeef19c806 (chrome -layer_tree_host.cc:198 ) cc::LayerTreeHost::~LayerTreeHost() 0x00005bbeef19ce2d (chrome -layer_tree_host.cc:171 ) cc::LayerTreeHost::~LayerTreeHost() 0x00005bbeef4a52c1 (chrome -memory:2399 ) ui::Compositor::~Compositor() 0x00005bbeef4a572d (chrome -compositor.cc:217 ) bool mojo::internal::ValidateMessagePayload<arc::mojom::internal::IntentHelperInstance_RequestUrlHandlerList_Params_Data>(mojo::Message const*, mojo::internal::ValidationContext*) 0x00005bbeef49bd2c (chrome -window_tree_host_platform.cc:75 ) std::__1::__unique_if<cc::RasterizeAndRecordBenchmark>::__unique_single std::__1::make_unique<cc::RasterizeAndRecordBenchmark, std::__1::unique_ptr<base::Value, std::__1::default_delete<base::Value> >, base::OnceCallback<void (std::__1::unique_ptr<base::Value, std::__1::default_delete<base::Value> >)> >(std::__1::unique_ptr<base::Value, std::__1::default_delete<base::Value> >&&, base::OnceCallback<void (std::__1::unique_ptr<base::Value, std::__1::default_delete<base::Value> >)>&&) 0x00005bbef019898b (chrome -ash_window_tree_host_platform.cc:39 ) std::__1::unique_ptr<cryptauth::CryptAuthEnrollerFactory, std::__1::default_delete<cryptauth::CryptAuthEnrollerFactory> >::unique_ptr(std::__1::unique_ptr<cryptauth::CryptAuthEnrollerFactory, std::__1::default_delete<cryptauth::CryptAuthEnrollerFactory> >&&) 0x00005bbef019fe77 (chrome -memory:2399 ) ash::RootWindowController::~RootWindowController() 0x00005bbef0191c0f (chrome -window_tree_host_manager.cc:228 ) ash::WindowTreeHostManager::Shutdown() 0x00005bbef01b5645 (chrome -shell.cc:813 ) ash::Shell::~Shell() 0x00005bbef01b68dd (chrome -shell.cc:660 ) <name omitted> 0x00005bbef06506c7 (chrome -ash_shell_init.cc:105 ) AshShellInit::~AshShellInit() 0x00005bbef049505c (chrome -memory:2399 ) ChromeBrowserMainExtraPartsAsh::PostMainMessageLoopRun() 0x00005bbeedb53f19 (chrome -chrome_browser_main.cc:2244 ) ChromeBrowserMainParts::PostMainMessageLoopRun() 0x00005bbeed00e04d (chrome -chrome_browser_main_chromeos.cc:1148 ) chromeos::ChromeBrowserMainPartsChromeos::PostMainMessageLoopRun() 0x00005bbeec68d53e (chrome -browser_main_loop.cc:1201 ) content::BrowserMainLoop::ShutdownThreadsAndCleanUp() 0x00005bbeec68fe50 (chrome -browser_main_runner.cc:205 ) content::BrowserMainRunnerImpl::Shutdown() 0x00005bbeec6891d4 (chrome -browser_main.cc:48 ) content::BrowserMain(content::MainFunctionParams const&) 0x00005bbeedb3fc90 (chrome -content_main_runner.cc:713 ) content::ContentMainRunnerImpl::Run() 0x00005bbeedb48e3b (chrome -main.cc:456 ) service_manager::Main(service_manager::MainParams const&) 0x00005bbeedb3e830 (chrome -content_main.cc:19 ) content::ContentMain(content::ContentMainParams const&) 0x00005bbeebee69d9 (chrome -chrome_main.cc:144 ) ChromeMain 0x00007fbff0e42735 (libc-2.23.so -libc-start.c:289 ) __libc_start_main 0x00005bbeebee66b8 (chrome + 0x010886b8 ) _start 0x00007ffe345f97a7 Crash ID link: https://crash.corp.google.com/browse?stbtiq=c23166dd07d90626#0 Repro scenario: Device was left idle for few minutes. On trying to unlock the user account, observed that lock screen was unresponsive and then user account was logged out automatically. Observed browser crash immediately after login to user account.
,
Feb 26 2018
Jacob could you take a look?
,
Mar 9 2018
This matches a lot of feedback reports igo@ has seen recently; I can paste crash and feedback links. One thing we notice often is that after the chrome crash, we also often see this in syslog: var/log/messages:2018-02-16T23:15:48.292559+00:00 CRIT ui-post-stop-unkillable[31217]: 25808 R< [chrome]
,
Mar 9 2018
This is pretty widespread on beta, it seems from reports. Bumping to P1.
,
Mar 9 2018
owner to marcheu@ since the stack looks like an issue with graphics. I did not see anything in the logs, except that chrome was shutting down. I'll upload a CL that adds a log message if the user pressed the "Shut down" button.
,
Mar 9 2018
,
Mar 9 2018
Reopening, I don't think this is the same bug. In this particular example, the IO thread is blocked on some networking thing: 0x00007fbff0f19e67 (libc-2.23.so -recv.c:28 ) __libc_recv 0x00005bbeee2c5337 (chrome -socket2.h:37 ) net::internal::AddressTrackerLinux::ReadMessages(bool*, bool*, bool*) 0x00005bbeee2c5010 (chrome -address_tracker_linux.cc:209 ) net::internal::AddressTrackerLinux::Init() 0x00005bbeee143f36 (chrome -network_interfaces_linux.cc:218 ) net::GetNetworkList(std::__1::vector<net::NetworkInterface, std::__1::allocator<net::NetworkInterface> >*, int) 0x00005bbeee144034 (chrome -network_interfaces_linux.cc:231 ) net::GetWifiSSID() 0x00005bbef009540b (chrome -data_reduction_proxy_config.cc:830 ) data_reduction_proxy::DataReductionProxyConfig::GetCurrentNetworkID() const 0x00005bbef0094f5b (chrome -data_reduction_proxy_config.cc:632 ) data_reduction_proxy::DataReductionProxyConfig::OnNetworkChanged(net::NetworkChangeNotifier::ConnectionType) 0x00005bbeebf64bbe (chrome -callback.h:94 ) base::ObserverListThreadSafe<base::FieldTrialList::Observer>::NotifyWrapper(base::FieldTrialList::Observer*, base::ObserverListThreadSafe<base::FieldTrialList::Observer>::NotificationData const&) 0x00005bbeebe32094 (chrome -callback.h:65 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) 0x00005bbeebe3342b (chrome -message_loop.cc:395 ) base::MessageLoop::RunTask(base::PendingTask*) 0x00005bbeebe33a5f (chrome -message_loop.cc:407 ) base::MessageLoop::DoWork() 0x00005bbeebe33d7c (chrome -message_pump_libevent.cc:220 ) base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) 0x00005bbeedea5af4 (chrome -run_loop.cc:133 ) network::mojom::internal::CookieDeletionSessionControl_Data::IsKnownValue(int) 0x00005bbeec697810 (chrome -browser_thread_impl.cc:215 ) content::BrowserThreadImpl::IOThreadRun(base::RunLoop*) 0x00005bbeec6978ab (chrome -browser_thread_impl.cc:242 ) content::BrowserThreadImpl::Run(base::RunLoop*) 0x00005bbeedeca438 (chrome -thread.cc:338 ) base::Thread::ThreadMain() 0x00005bbeedec5a5c (chrome -platform_thread_posix.cc:75 ) base::(anonymous namespace)::ThreadFunc(void*) 0x00007fbff1dda2b7 (libpthread-2.23.so -pthread_create.c:333 ) start_thread 0x00007fbff0f18fac (libc-2.23.so + 0x000f6fac ) clone Blocking the IO thread will for sure block the UI. This is a no-no. ->pauljensen who seems to be doing work in the area.
,
Mar 12 2018
Looks like Issue 806125
,
May 30 2018
Issue 835519 has been merged into this issue. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by sdantul...@chromium.org
, Feb 16 2018