New issue
Advanced search Search tips

Issue 705758 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Crash in chromeos::EnterpriseEnrollmentHelperImpl::DoEnroll on 'Stout'

Project Member Reported by keta...@chromium.org, Mar 27 2017

Issue description

Report ID48c5c01640000000
Product, versionChrome_ChromeOS, 57.0.2987.123
Process typebrowser

Magic Signaturechromeos::EnterpriseEnrollmentHelperImpl::DoEnrolledit bugs&comments
Stable Signaturechromeos::EnterpriseEnrollmentHelperImpl::DoEnroll-7290da97edit bugs&comments
Report TimeMon, 27 Mar 2017 22:35:25 GMT
Uptime23494 ms

Component: 	src/chrome/browser/chromeos/login/enrollment
File path: 	src/chrome/browser/chromeos/login/enrollment/enterprise_enrollment_helper_impl.cc

Client ID661d6da06b26411589c94254a76176b7
FilesminidumpDownloadchrome.txtDownloadView filei915_error_state.log.xzDownloadView file
In shutdownfalse
Device Modelstout-signed-mp-v4keys
Thread 0 CRASHED [SIGILL @ 0x00007f7efa264f60 ] MAGIC SIGNATURE THREAD
Stack Quality94%Show frame trust levels
0x00007f7efa264f60	(chrome -enterprise_enrollment_helper_impl.cc:164 )	chromeos::EnterpriseEnrollmentHelperImpl::DoEnroll(std::string const&)
0x00007f7efa264c94	(chrome -enterprise_enrollment_helper_impl.cc:221 )	chromeos::EnterpriseEnrollmentHelperImpl::OnTokenFetched(bool, std::string const&, GoogleServiceAuthError const&)
0x00007f7efa31a8c7	(chrome -callback.h:85 )	PolicyOAuth2TokenFetcherImpl::OnGetTokenSuccess
0x00007f7ef92303d3	(chrome -oauth2_access_token_fetcher_impl.cc:248 )	OAuth2AccessTokenFetcherImpl::EndGetAccessToken(net::URLFetcher const*)
0x00007f7ef8f60dac	(chrome -callback.h:68 )	base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*)
0x00007f7ef8f4cca1	(chrome -message_loop.cc:421 )	base::MessageLoop::DoWork()
0x00007f7ef8f4d332	(chrome -message_pump_libevent.cc:218 )	base::MessagePumpLibevent::Run(base::MessagePump::Delegate*)
0x00007f7efa8f9f97	(chrome -run_loop.cc:37 )	base::RunLoop::Run()
0x00007f7efa5d4ca5	(chrome -chrome_browser_main.cc:1977 )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x00007f7ef9bfd0da	(chrome -browser_main_loop.cc:1182 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x00007f7ef9c00214	(chrome -browser_main_runner.cc:141 )	content::BrowserMainRunnerImpl::Run()
0x00007f7ef9bf9f0b	(chrome -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const&)
0x00007f7efa57d8d9	(chrome -content_main_runner.cc:793 )	content::ContentMainRunnerImpl::Run()
0x00007f7efa57c57a	(chrome -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x00007f7ef91be15a	(chrome -chrome_main.cc:112 )	ChromeMain
0x00007f7ef6816795	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x00007f7ef91bdf78	(chrome + 0x011e5f78 )	_start
0x00007ffe6e72aa57		

abodenha@ this is an enterprise enrollment related crash. Who can look at this one? This is currently 10% of all crashes on stout.
 
Cc: r...@chromium.org
Components: Enterprise>Enrollment UI>Shell>OOBE
Owner: drcrash@chromium.org
Status: Assigned (was: Untriaged)
Owner: tnagel@chromium.org
tnagel@ owns enterprise enrollment.

Comment 4 by tnagel@chromium.org, Apr 19 2017

This is crashing in EnterpriseEnrollmentHelperImpl::DoEnroll() at CHECK(dcp_initializer).  From my reading of the code, the initializer can be nullptr when the SystemSaltGetter or the DBusThreadManager are not ready when BrowserPolicyConnectorChromeOS constructor runs which then fails to create a DeviceCloudPolicyManager which then in turns leads to the DeviceCloudPolicyInitializer not being created.

Comment 5 by tnagel@chromium.org, Apr 21 2017

Cc: tnagel@chromium.org
Labels: -Pri-1 Pri-2
Owner: atwilson@chromium.org
Hey Drew, we've seen a total of ~500 enrollment crashes due to this issue:   303  stout, 55 terra, 23 candy, 20 daisy, ...  (Not sure which fraction of crashes is uploaded, though.)

The problem looks like yet another race that is only triggered on specific boards and only under specific circumstances (unclear which).  Could you please prioritize and assign?
Owner: igorcov@chromium.org
Igor, not a super high priority, but would be useful to do some forensics here. Probably hard to diagnose without logs, though we could add different CHECK() lines to figure out why dcp_initializer is null.
Components: -UI>Shell>OOBE

Sign in to add a comment