GitLab

Mash services like tap_visualizer are launched as utility processes
so Chrome's crash reporting system works fine with them. Using chrome's
crash system gives us Chrome's version number for the crashes (which
makes sense, since the services are built into the chrome binary),
support for chrome-specific crash features like crash-keys, etc.

Override the process type with the service name so these crashes
show up independently in the crash console, similar to what we do for
extension renderers.

Bug: 846123
Test: browser_tests, also kill -SEGV the tap_visualizer process and check reports
Change-Id: I133aedcf1f263beb2d349e9bc24e5b3624d03ea8
Reviewed-on: https://chromium-review.googlesource.com/1072205Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#561656}