Forked from issue 771801
* Run chrome --mash
* Find the ash process (it will be --type=utility, but you'll need to look at log spam to find the pid)
* kill -SIGSEGV <pid>
Everything should quit, but it doesn't.
Note that testing Ctrl-C in the main terminal is not sufficient. That will kill the browser, which will bring down ash and appear to work.
This probably broke with sky's recent change to move service manager back into browser.
Comment 1 by jamescook@chromium.org
, Oct 12 2017