Issue metadata
Sign in to add a comment
|
renderer crash on login window |
||||||||||||||||||||||
Issue descriptionNot sure if there's a bug already. TOT chrome (as of just now) crashes on kevin in a loop on the login screen: [5153:5153:0111/151230.420405:FATAL:login_display_host_webui.cc(796)] Renderer crash on login window #0 0x00000906a638 base::debug::StackTrace::StackTrace() #1 0x000009006c06 logging::LogMessage::~LogMessage() #2 0x0000082e9442 chromeos::LoginDisplayHostWebUI::RenderProcessGone() #3 0x000007dd55a6 content::WebContentsImpl::RenderViewTerminated() #4 0x000007d1a044 content::RenderProcessHostImpl::ProcessDied() #5 0x00000900b398 base::debug::TaskAnnotator::RunTask() #6 0x00000900abfc base::MessageLoopImpl::RunTask() #7 0x00000900af84 base::MessageLoopImpl::DoWork() #8 0x0000090780f4 base::MessagePumpLibevent::Run() #9 0x00000902172c base::RunLoop::Run() #10 0x000008d99ab4 ChromeBrowserMainParts::MainMessageLoopRun() #11 0x000007b2a1be content::BrowserMainLoop::RunMainMessageLoopParts() #12 0x000007b2bbc0 content::BrowserMainRunnerImpl::Run() #13 0x000007b27efa content::BrowserMain() #14 0x000008d90e44 content::ContentMainRunnerImpl::RunServiceManager() #15 0x000008d90bd8 content::ContentMainRunnerImpl::Run() #16 0x000008d94ef8 service_manager::Main() #17 0x000008d8f9c6 content::ContentMain() #18 0x00000740a188 ChromeMain #19 0x0000ef8c10a2 __libc_start_main
,
Jan 12
To clarify, was this a chrome_internal build of kevin? Issue 917504 is only applicable (AFAIK) to builds of Chrome which aren't both branded and official. If it isn't a chrome_internal build, https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1405444 should work around the crash. If this is blocking you in any way, you should be able to re-`emerge` chromeos-chrome with USE='-lld gold'.
,
Jan 12
can you please clarify how you built this chrome? simple chrome? which flags? Just want to verify you are hitting this problem under the same circumstances we have seen it. Thanks bpastene for duplicating.
,
Jan 12
I don't think this was a chrome_internal build; I believe I need to pass in --internal to cros chrome-sdk for that. My steps: cros chrome-sdk --debug--board=kevin autoninja -C out_$SDK_BOARD/Release/ chromiumos_preflight deploy_chrome --build-dir=out_kevin/Release --to=100.90.29.199 The screen flashes, and I can see new chrome log files being created, each with a stack. To get the actual stack, I did: deploy_chrome --build-dir=out_kevin/Release --mount --nostrip --to=100.90.29.199 My SDK version is R73-11549.0.0
,
Jan 12
Chrome is at b913f5d056b664035a1cd050cbc0ec03a9605a2d, timestamp is Fri Jan 11 22:52:27
,
Jan 12
So I guess this is to be expected. I'll try with --internal to see if that helps
,
Jan 15
Yup, no problems with --internal. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bpastene@chromium.org
, Jan 11Status: Duplicate (was: Untriaged)