New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 599561 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 563716
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Telemetry benchmark fails to produce browser crash dumps on Win & Mac

Project Member Reported by nedngu...@google.com, Mar 31 2016

Issue description

A cl landed (suspecting https://codereview.chromium.org/1850703002) recently that cause many telemetry benchmarks on perf waterfall to fail due to the browser crashes.

However, Telemetry fails to output the crashdump of the browser when it crashes.

https://build.chromium.org/p/chromium.perf/builders/Win%20Zenbook%20Perf%20%283%29/builds/1299/steps/tracing.tracing_with_debug_overhead/logs/stdio

DevtoolsTargetCrashException: Devtools target crashed
********************************************************************************
(C:\b\build\slave\Win_Zenbook_Perf__3_\build\src\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py:341 _AddDebuggingInformation) Received a socket error in the browser connection and the tab no longer exists. The tab probably crashed.
********************************************************************************
(C:\b\build\slave\Win_Zenbook_Perf__3_\build\src\third_party\catapult\telemetry\telemetry\internal\backends\chrome_inspector\inspector_backend.py:342 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:59160/devtools/page/94ECCAFA-1491-435C-AC6D-2F6D09071B0C
Stack Trace:
********************************************************************************
	No crash dump found.
********************************************************************************
Standard output:
********************************************************************************
********************************************************************************

Mac:
DevtoolsTargetCrashException: Devtools target crashed
********************************************************************************
(/b/build/slave/Mac_10_11_Perf__4_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:341 _AddDebuggingInformation) Received a socket error in the browser connection and the tab no longer exists. The tab probably crashed.
********************************************************************************
(/b/build/slave/Mac_10_11_Perf__4_/build/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:342 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:63808/devtools/page/35AA3190-F28D-4568-8B13-F4AF4CCE98A0
Stack Trace:
********************************************************************************
	No crash dump found.
********************************************************************************
Standard output:
********************************************************************************
	2016-03-31 04:29:37.465 Google Chrome[20971:57904] NSWindow warning: adding an unknown subview: <FullSizeContentView: 0x7fd61970dc40>. Break on NSLog to debug.
	2016-03-31 04:29:37.465 Google Chrome[20971:57904] Call stack:
	(
	    "+callStackSymbols disabled for performance reasons"
	)
	Mar 31 04:29:49  Google Chrome Helper[20980] <Error>: CGAffineTransformInvert: singular matrix.
	Mar 31 04:29:50  Google Chrome Helper[20980] <Error>: CGAffineTransformInvert: singular matrix.
********************************************************************************


According to Sami, to produce the crash dump, he has to start telemetry with "--extra-browser-args=--disable-breakpad".
 
Mergedinto: 563716
Status: Duplicate (was: Untriaged)

Sign in to add a comment