Chrome crashes normally indicate the process type which crashed - WebView microdumps don't include this information, and so there's no way to easily tell (or filter on) whether a crash was in single process or multiprocess mode, and if multiprocess, whether it was a browser or renderer crash.

We should probably include this information in the microdump so that the crash frontend can expose it and allow easy filtering (so that we can spot multiprocess-specific issues, or ignore multiprocess-mode crashes when looking at general release stability). We may want to just try to expose the same process type information that Chrome uses, so that it can be handled the same way?

It's possible to tell this *indirectly* in some cases: e.g. the process name is a big hint to see if it's a renderer crash, but it's not easy to filter by that, and there's not really any way to tell the difference between a browser crash in single vs multiprocess mode.