mash: Exit main process if content_browser service crashes

chrome/app/mash/chrome_mash_manifest.json

Index: chrome/app/mash/chrome_mash_manifest.json
diff --git a/chrome/app/mash/chrome_mash_manifest.json b/chrome/app/mash/chrome_mash_manifest.json
index c3a87d2a6d7786cb50b4e21b1f0a5d3012115bc2..d25ed498d4ffc46d322df9ac37348d6c18b4bb55 100644
--- a/chrome/app/mash/chrome_mash_manifest.json
+++ b/chrome/app/mash/chrome_mash_manifest.json
@@ -18,6 +18,7 @@
         "service_manager": [ "service_manager:instance_per_child" ],
         "catalog": [ "control" ],
         "ash": [ "app" ],
+        "content_browser": [ "app" ],

[James Cook, 2017/02/08 22:07:54]

This works, but I'm not sure why. In particular, content_browser_manifest.json
does not provide an "app" capability list. I'm not sure if "app" is special
somehow -- I didn't see anything in
https://chromium.googlesource.com/chromium/src/+/master/services/service_mana...
about special capabilities. Without this, though, mash_runner can't connect to
content_browser.

[Ken Rockot(use gerrit already), 2017/02/08 23:04:07]

I think it's because you need to have *some* requires entry for the service for
the service manager to consider allowing connection at all. You could probably
change "app" to anything and it would still work.

We probably need to look at making this less weird.

         "quick_launch": [ "app" ],
         "ui": [ "app" ]
       }