New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 636508 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crash:- CoreOobeHandler::ShowDeviceResetScreen

Project Member Reported by rookrishna@chromium.org, Aug 10 2016

Issue description

Chrome os version 53.0.2785.55/8530.49.0 cyan

Report ID9188c46900000000

Product, versionChrome_ChromeOS, 53.0.2785.55
Process typebrowser
Magic Signaturechromeos::CoreOobeHandler::ShowDeviceResetScreenedit bugs&comments
Stable Signaturechromeos::CoreOobeHandler::ShowDeviceResetScreen-ee6453f8edit bugs&comments
Report TimeWed, 10 Aug 2016 19:32:56 GMT
Uptime815056 ms
Client ID9d7cd2fa54a14eef97abc5b5432b9a0d
Filesminidumpchrome.txti915_error_state.log.xz
In shutdownfalse
Device Modelcyan-signed-mpkeys
Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
0x00007f983e907437	(chrome -core_oobe_handler.cc:218 )	chromeos::CoreOobeHandler::ShowDeviceResetScreen
0x00007f983e7c8fc3	(chrome -signin_screen_handler.cc:1180 )	chromeos::SigninScreenHandler::HandleAccountPickerReady
0x00007f983ec84da0	(chrome -callback.h:389 )	content::WebUIImpl::ProcessWebUIMessage
0x00007f983ec85fab	(chrome -tuple.h:140 )	content::WebUIImpl::OnMessageReceived
0x00007f983c384dad	(chrome -web_contents_impl.cc:623 )	content::WebContentsImpl::OnMessageReceived
0x00007f983ebe755f	(chrome -render_view_host_impl.cc:837 )	content::RenderViewHostImpl::OnMessageReceived
0x00007f983ebf3769	(chrome -render_widget_host_impl.cc:444 )	content::RenderWidgetHostImpl::OnMessageReceived
0x00007f983ebe29c9	(chrome -render_process_host_impl.cc:1772 )	content::RenderProcessHostImpl::OnMessageReceived
0x00007f983cf2cbd5	(chrome -ipc_channel_proxy.cc:284 )	IPC::ChannelProxy::Context::OnDispatchMessage
0x00007f983bf602bc	(chrome -callback.h:389 )	base::debug::TaskAnnotator::RunTask
0x00007f983bf4e8c5	(chrome -message_loop.cc:493 )	base::MessageLoop::DoWork
0x00007f983bf483f2	(chrome -message_pump_libevent.cc:217 )	base::MessagePumpLibevent::Run
0x00007f983c8113b7	(chrome -run_loop.cc:35 )	base::RunLoop::Run
0x00007f983ff46a04	(chrome -chrome_browser_main.cc:1943 )	ChromeBrowserMainParts::MainMessageLoopRun
0x00007f983ed0a9ba	(chrome -browser_main_loop.cc:942 )	content::BrowserMainLoop::RunMainMessageLoopParts
0x00007f983eb41874	(chrome -browser_main_runner.cc:155 )	content::BrowserMainRunnerImpl::Run
0x00007f983eb41752	(chrome -browser_main.cc:46 )	content::BrowserMain
0x00007f983c7beb00	(chrome -content_main_runner.cc:785 )	content::ContentMainRunnerImpl::Run
0x00007f983c7bd5da	(chrome -content_main.cc:20 )	content::ContentMain
0x00007f983c44c41e	(chrome -chrome_main.cc:84 )	ChromeMain
0x00007f9839837fb5	(libc-2.19.so -libc-start.c:292 )	__libc_start_main
0x00007f983c44c286	(chrome + 0x011bf286 )	_start
 
Components: UI
Crash is seen after signout and sign back in . 
Labels: Stability-Crash
Owner: rookrishna@chromium.org
Status: Assigned (was: Untriaged)
Per triage: can you please provide more detailed repro steps? Thanks. 
Status: WontFix (was: Assigned)
Looks like the Hardware ID change on the device was causing this crash. Unable to repro the crash after Hardware ID was corrected .Closing the bug

Sign in to add a comment