We are seeing one of the top R55 crashes at mojo::edk::Waiter::Wait
Report ID9f63c61b00000000
Product, versionChrome_ChromeOS, 55.0.2883.29
Process typebrowser
Magic Signaturemojo::edk::Waiter::Waitedit bugs&comments
Stable Signaturemojo::edk::Waiter::Wait-39291308edit bugs&comments
Report TimeTue, 01 Nov 2016 11:58:34 GMT
Uptime73528049 ms
Client IDb89a17d3d7714b1ab43511d5d1a80aae
Filesminidumpchrome.txti915_error_state.log.xz
In shutdownfalse
Device Modelgnawty-signed-mp-v3keys
Thread 0 CRASHED [SIGABRT @ 0x000003e8000002a8 ] MAGIC SIGNATURE THREAD
0x00007fe2d528717c (libpthread-2.19.so + 0x0000c17c ) pthread_cond_wait
0x00007fe2d8b6b4ef (chrome -waiter.cc:64 ) mojo::edk::Waiter::Wait
0x00007fe2d66cf4aa (chrome -core.cc:1169 ) mojo::edk::Core::Wait
0x00007fe2d666a736 (chrome -handle.h:191 ) mojo::SyncHandleRegistry::WatchAllHandles
0x00007fe2d8705872 (chrome -ipc_sync_channel.cc:620 ) IPC::SyncChannel::WaitForReply
0x00007fe2d66902c2 (chrome -ipc_sync_channel.cc:584 ) IPC::SyncChannel::Send
0x00007fe2d6aa24c1 (chrome -command_buffer_proxy_impl.cc:701 ) gpu::CommandBufferProxyImpl::Send
0x00007fe2d6aa30c7 (chrome -command_buffer_proxy_impl.cc:363 ) gpu::CommandBufferProxyImpl::WaitForGetOffsetInRange
0x00007fe2d6a9e387 (chrome -cmd_buffer_helper.cc:168 ) gpu::CommandBufferHelper::WaitForGetOffsetInRange
0x00007fe2d6a9e541 (chrome -cmd_buffer_helper.cc:222 ) gpu::CommandBufferHelper::Finish
0x00007fe2d8b16064 (chrome -gles2_implementation.cc:464 ) gpu::gles2::GLES2Implementation::WaitForCmd
0x00007fe2d8b19300 (chrome -gles2_implementation.cc:369 ) gpu::gles2::GLES2Implementation::FreeEverything
0x00007fe2d8b1252b (chrome -gles2_implementation.cc:428 ) gpu::gles2::GLES2Implementation::SetAggressivelyFreeResources
0x00007fe2d87a20de (chrome -context_cache_controller.cc:166 ) cc::ContextCacheController::OnIdle
0x00007fe2d661f54c (chrome -callback.h:64 ) base::debug::TaskAnnotator::RunTask
0x00007fe2d660dc9c (chrome -message_loop.cc:405 ) base::MessageLoop::DoDelayedWork
0x00007fe2d660eeee (chrome -message_pump_libevent.cc:227 ) base::MessagePumpLibevent::Run
0x00007fe2d7e71e07 (chrome -run_loop.cc:35 ) base::RunLoop::Run
0x00007fe2d7b5ca24 (chrome -chrome_browser_main.cc:2116 ) ChromeBrowserMainParts::MainMessageLoopRun
0x00007fe2d723134a (chrome -browser_main_loop.cc:981 ) content::BrowserMainLoop::RunMainMessageLoopParts
0x00007fe2d7233044 (chrome -browser_main_runner.cc:155 ) content::BrowserMainRunnerImpl::Run
0x00007fe2d722dc3b (chrome -browser_main.cc:46 ) content::BrowserMain
0x00007fe2d7aff050 (chrome -content_main_runner.cc:779 ) content::ContentMainRunnerImpl::Run
0x00007fe2d7afdbea (chrome -content_main.cc:20 ) content::ContentMain
0x00007fe2d6884195 (chrome -chrome_main.cc:97 ) ChromeMain
0x00007fe2d3edcfb5 (libc-2.19.so -libc-start.c:292 ) __libc_start_main
0x00007fe2d6883fe4 (chrome + 0x011c6fe4 ) _start
0x00007ffec2de8447
Comment 1 by bhthompson@google.com
, Nov 1 2016