No description
2f3ed034f3
At some point Chrome started naming its threads such that crashes report a different executable name. We've been getting a *lot* of crash-reporter errors with names like "supplied_Compositor" in particular, so consider those to be Chrome crashes that should be ignored. Unfortunately, the thread names can be arbitrary. With this CL we check the entire range of possible names. Maybe someday someone can use the core file to determine that a process was originally named "chrome". BUG=chrome-os-partner:12045 TEST=Ran unittests Change-Id: Ia82d619bd1ee4367129640dc6c7be5ce258a68bb Reviewed-on: https://gerrit.chromium.org/gerrit/31084 Commit-Ready: Michael Krebs <mkrebs@chromium.org> Tested-by: Michael Krebs <mkrebs@chromium.org> Reviewed-by: Ben Chan <benchan@chromium.org> |
||
|---|---|---|
| crash_reporter | ||