Chrome Version: ToT (r616367)
OS: ChromeOS

What steps will reproduce the problem?
(1) ./out/Debug/chrome
(2) close (ctrl-shift-q twice)

What is the expected result?
Chrome finishes successfully

What happens instead?
Crash:

Received signal 11 <unknown> 000000000000
#0 0x7f7d994d828d base::debug::StackTrace::StackTrace()
#1 0x7f7d991e902a base::debug::StackTrace::StackTrace()
#2 0x7f7d994d7d0f base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f7d642740c0 <unknown>
#4 0x555ed1b604d1 gcm::GCMDriver::Shutdown()
#5 0x555ed1bbb597 gcm::GCMDriverDesktop::Shutdown()
#6 0x555ed1b64fb8 gcm::GCMProfileService::Shutdown()
#7 0x7f7d8ea672d8 KeyedServiceFactory::ContextShutdown()
#8 0x7f7d856ad578 BrowserContextKeyedServiceFactory::BrowserContextShutdown()
#9 0x7f7d856ad6dc BrowserContextKeyedServiceFactory::ContextShutdown()
#10 0x7f7d8ea61f5d DependencyManager::DestroyContextServices()
#11 0x7f7d856aa3e8 BrowserContextDependencyManager::DestroyBrowserContextServices()
#12 0x555ece3e73aa ProfileImpl::~ProfileImpl()
#13 0x555ece3e7c69 ProfileImpl::~ProfileImpl()
#14 0x555ece3f43f6 ProfileDestroyer::DestroyProfileWhenAppropriate()
#15 0x555ece452ff6 ProfileManager::ProfileInfo::~ProfileInfo()
#16 0x555ece4572de std::__1::pair<>::~pair()
#17 0x555ece4574cd std::__1::__tree<>::destroy()
#18 0x555ece4573df std::__1::__tree<>::~__tree()
#19 0x555ece456e45 std::__1::map<>::~map()
#20 0x555ece43f03f ProfileManager::~ProfileManager()
#21 0x555ece43f199 ProfileManager::~ProfileManager()
#22 0x555ecde930a3 BrowserProcessImpl::StartTearDown()
#23 0x555ecde8af94 ChromeBrowserMainParts::PostMainMessageLoopRun()
#24 0x555ecc64e7f8 chromeos::ChromeBrowserMainPartsChromeos::PostMainMessageLoopRun()
#25 0x7f7d92641e6b content::BrowserMainLoop::ShutdownThreadsAndCleanUp()
#26 0x7f7d92649ce7 content::BrowserMainRunnerImpl::Shutdown()
#27 0x7f7d92634b9d content::BrowserMain()
#28 0x7f7d9456b050 content::RunBrowserProcessMain()
#29 0x7f7d9456e4c5 content::ContentMainRunnerImpl::RunServiceManager()
#30 0x7f7d9456d089 content::ContentMainRunnerImpl::Run()
#31 0x7f7d94563e6c content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#32 0x7f7d99781ac1 service_manager::Main()
#33 0x7f7d94568765 content::ContentMain()
#34 0x555eca09c246 ChromeMain
#35 0x555eca09c152 main
#36 0x7f7d621002b1 __libc_start_main
#37 0x555eca09c02a _start
  r8: 0000000000000001  r9: 0000000000000001 r10: 00007ffc3a205f20 r11: 0000000000000000
 r12: 0000555eca09c000 r13: 00007ffc3a20c090 r14: 0000000000000000 r15: 0000000000000000
  di: 00002894dbd25070  si: 00007ffc3a2062b0  bp: 00007ffc3a206830  bx: 0000000000000000
  dx: 00007ffc3a2062b0  ax: 00002894dbd25070  cx: 3636363636363636  sp: 00007ffc3a2064c0
  ip: 0000555ed1b604d1 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000000
 trp: 000000000000000d msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]




Please use labels and text to provide additional information.

If this is a regression (i.e., worked before), please consider using the
bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help
us identify the root cause and more rapidly triage the issue.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.