Descriptionmash: Exit main process if content_browser service crashes
For the ash/browser and window-server/browser connections both sides cache
information about the other side. For now, rather than trying to make the
services restartable we just bring down the main chrome --mash root process.
The Chrome OS session_manager will then restart everything.
Also explicitly start content_browser on startup, like mash_session used to
do. It provides interfaces needed by ash (prefs, login state) that we're
going to need for a while.
BUG=678683
TEST=navigate to about:inducebrowsercrashforrealz, root process exits
Review-Url: https://codereview.chromium.org/2686003002
Cr-Commit-Position: refs/heads/master@{#450506}
Committed: https://chromium.googlesource.com/chromium/src/+/896d1d57393c5a0d787210a3e24007e973fb2fe5
Patch Set 1 #
Total comments: 2
Patch Set 2 : rebase #Patch Set 3 : rebase #
Messages
Total messages: 14 (9 generated)
|