ChromeDriver tests can automatically include diagnostic information from minidumps in failures |
|
Issue descriptionkbr@ wrote in issue 858922 : """ Here's the code in Telemetry that gets a stack trace from a minidump: https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py?type=cs&q=_GetStackFromMinidump&sq=package:chromium&g=0&l=420 The code which can enumerate all unsymbolized minidumps: https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py?type=cs&q=GetAllUnsymbolizedMinidumpPaths&sq=package:chromium&g=0&l=514 and the code which automatically appends the symbolized minidump to the AppCrashException which is propagated through Telemetry if something goes wrong with the browser: https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/core/exceptions.py?type=cs&q=_minidump_path&sq=package:chromium&g=0&l=74 Hopefully some of this scaffolding could be integrated into WebDriver. There are still issues like if both the GPU and a renderer process crash we don't see both minidumps, but this would at least be a start if it were integrated into WebDriver. """ If we pull at least a stack trace out of a minidump, then it could help with issues like issue 864205 as well. |
|
►
Sign in to add a comment |
|
Comment 1 by crouleau@chromium.org
, Jul 18env['BREAKPAD_DUMP_LOCATION'] = self._tmp_minidump_dir from https://cs.chromium.org/chromium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/desktop_browser_backend.py?type=cs&q=_GetStackFromMinidump&sq=package:chromium&g=0&l=420 Thanks John!