I regularly see my local runs of android layout tests fail because of this check:

18:17:32.614 15643   03-26 01:16:18.497  4899  4930 F chromium: [4899:4930:0326/011618:206540309:FATAL:crash_dump_manager_android.cc(35)] Check failed: instance_.

I've also seen this on the bots, but somehow they still pass:
https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/44920/steps/steps/logs/stdio
(log attached in case that link breaks)

Who owns the crash manager? This code seems really prone to racing. It wants to be a singleton, but the pattern is really strange and there's no atomic state AFAIK. 

The call stack at the time of the crash is:
  00439349  logging::LogMessage::~LogMessage()
  0282eb0b  breakpad::CrashDumpManager::GetInstance()
  0033ea27  content::ShellContentBrowserClient::GetAdditionalMappedFilesForChildProcess(...) 
  01fa05b9  LaunchOnLauncherThread
  ... CLIPPED BIND STUFF ...
  0043de89  base::MessageLoop::RunTask(base::PendingTask const&)
  0043e49d  base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&)
  0043e579  base::MessageLoop::DoWork()
  0043fc51  base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
  0043f5f7  base::MessageLoop::RunHandler()
  0045286f  base::RunLoop::Run()
  0043dbff  base::MessageLoop::Run()
  01f897b1  content::BrowserThreadImpl::ProcessLauncherThreadRun(base::MessageLoop*)                                                                                                                         01f899b7  content::BrowserThreadImpl::Run(base::MessageLoop*)
 

Deleted: webkit_nexus_4_build_44920.log 4.1 MB

webkit_nexus_4_build_44920.log 4.1 MB View Download