Fix shutdown crash by ensuring valid MessageLoop

services/service_manager/public/cpp/lib/service_runner.cc

Index: services/service_manager/public/cpp/lib/service_runner.cc
diff --git a/services/service_manager/public/cpp/lib/service_runner.cc b/services/service_manager/public/cpp/lib/service_runner.cc
index 99e1130ff53062d616b2b24490b8d33d3894539b..374a9483ca2416a4237a8cee6db957951a6be308 100644
--- a/services/service_manager/public/cpp/lib/service_runner.cc
+++ b/services/service_manager/public/cpp/lib/service_runner.cc
@@ -59,13 +59,6 @@ MojoResult ServiceRunner::Run(MojoHandle service_request_handle,
     base::RunLoop run_loop;
     context_->SetConnectionLostClosure(run_loop.QuitClosure());
     run_loop.Run();
-    // It's very common for the service to cache the app and terminate on
-    // errors. If we don't delete the service before the app we run the risk of
-    // the service having a stale reference to the app and trying to use it.
-    // Note that we destruct the message loop first because that might trigger
-    // connection error handlers and they might access objects created by the
-    // service.
-    loop.reset();
     context_.reset();
   }
   return MOJO_RESULT_OK;