Fix enrollment crash when using requisition parameter |
||||||||
Issue description[949:949:1122/110851:FATAL:url_fetcher_core.cc(108)] Check failed: original_url_.is_valid(). #0 0x7fda3e44080e base::debug::StackTrace::StackTrace() #1 0x7fda3e4623ea logging::LogMessage::~LogMessage() #2 0x7fda3de03f8a net::URLFetcherCore::URLFetcherCore() #3 0x7fda3de08e74 net::URLFetcherImpl::URLFetcherImpl() #4 0x7fda3de03a67 net::URLFetcher::Create() #5 0x7fda3a61d640 policy::DeviceManagementService::StartJob() #6 0x7fda3a60894b policy::CloudPolicyClient::Register() #7 0x7fda3f5269e6 policy::EnrollmentHandlerChromeOS::StartRegistration() #8 0x7fda3f525c82 policy::EnrollmentHandlerChromeOS::HandleStateKeysResult() #9 0x7fda3f53390a policy::ServerBackedStateKeysBroker::RequestStateKeys() #10 0x7fda3f5257e0 policy::EnrollmentHandlerChromeOS::StartEnrollment() #11 0x7fda3f50ab05 policy::DeviceCloudPolicyInitializer::StartEnrollment() #12 0x7fda3f450a76 chromeos::EnterpriseEnrollmentHelperImpl::DoEnroll() #13 0x7fda3f45074d chromeos::EnterpriseEnrollmentHelperImpl::EnrollUsingToken() #14 0x7fda3f52e84d policy::(anonymous namespace)::PolicyOAuth2TokenFetcherImpl::OnGetTokenSuccess() #15 0x7fda3f03aba8 OAuth2AccessTokenFetcherImpl::EndGetAccessToken() #16 0x7fda3f03b159 OAuth2AccessTokenFetcherImpl::OnURLFetchComplete() #17 0x7fda3de07b36 net::URLFetcherCore::OnCompletedURLRequest() #18 0x7fda3e44132e base::debug::TaskAnnotator::RunTask() #19 0x7fda3e46ea1d base::MessageLoop::RunTask() #20 0x7fda3e46ed88 base::MessageLoop::DeferOrRunPendingTask() #21 0x7fda3e46f19b base::MessageLoop::DoWork() #22 0x7fda3e470fba base::(anonymous namespace)::WorkSourceDispatch() #23 0x7fda3702ce04 g_main_context_dispatch #24 0x7fda3702d048 <unknown> #25 0x7fda3702d0ec g_main_context_iteration #26 0x7fda3e470d86 base::MessagePumpGlib::Run() #27 0x7fda3e46e729 base::MessageLoop::RunHandler() #28 0x7fda3e49d3f0 base::RunLoop::Run() #29 0x7fda3f86ff59 ChromeBrowserMainParts::MainMessageLoopRun() #30 0x7fda3bdd75f9 content::BrowserMainLoop::RunMainMessageLoopParts() #31 0x7fda3bdda6e0 content::BrowserMainRunnerImpl::Run() #32 0x7fda3bdd2f0e content::BrowserMain() #33 0x7fda3c50f203 content::ContentMainRunnerImpl::Run() #34 0x7fda3c50dc80 content::ContentMain() #35 0x7fda3f020b13 ChromeMain #36 0x7fda343dbf45 __libc_start_main #37 0x7fda3f0209b1 <unknown>
,
Nov 22 2016
Actually, this is just due to a bad --device-management-url parameter (missing the scheme).
,
Nov 22 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/7ddc6470f6a0dadef7eac16630e8cca4ba795d3f commit 7ddc6470f6a0dadef7eac16630e8cca4ba795d3f Author: tnagel <tnagel@chromium.org> Date: Tue Nov 22 15:14:02 2016 Add DCHECK() for invalid URL in DeviceManagementService::StartJob() BUG= 667710 Review-Url: https://codereview.chromium.org/2514263004 Cr-Commit-Position: refs/heads/master@{#433860} [modify] https://crrev.com/7ddc6470f6a0dadef7eac16630e8cca4ba795d3f/components/policy/core/common/cloud/device_management_service.cc
,
Nov 22 2016
,
Jan 9 2017
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Jul 6 2017
bulk Verify of older or not-user-facing Chromad bugs |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 Deleted