Crash metrics: failure to reach handler / unresponsive handler |
|||
Issue descriptionGet metrics for: 1) failure to reach handler on crash https://cs.chromium.org/chromium/src/third_party/crashpad/crashpad/client/crashpad_client_win.cc?l=130 2) crash server unresponsive https://cs.chromium.org/chromium/src/third_party/crashpad/crashpad/client/crashpad_client_win.cc?l=172
,
Feb 28 2017
Do you mean to get uma? Is the concern that there won't be time to write data before it terminates itself? In both of those cases, it'd be fine to flush "something" since things are in a pretty bad state, it can't hurt to try to record some data. Having said that, those should appear in CrashExitCodes.Renderer already because they have a distinct exit code. It looks like for yesterday's Canary they account for 00.22% of exit codes.
,
Feb 28 2017
Oh, right we have uma for the exit code. Looks like it's also small for the browser (Stability.BrowserExitCodes is 0.02%). Forget I said anything! :) |
|||
►
Sign in to add a comment |
|||
Comment 1 by manzagop@chromium.org
, Feb 28 2017