Friendly sheriff ping

(According to the Perf Bot Sheriffing guide, Pri-1 build bot bugs should be pinged daily. Please close the issue if it's already been fixed.)

Chrome is crashing with segfault. So this is not a problem in the benchmark but rather a bug in Chrome.

Unfortunately, the stack trace is not symbolized:


(/b/c/b/Mac_Retina_Perf__4_/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:411 _AddDebuggingInformation) Debugger url: ws://127.0.0.1:53836/devtools/page/e9b9bd3d-bc4e-4609-a2d9-c45c7e16386f
Found Minidump: True
Stack Trace:
********************************************************************************
	Operating system: Mac OS X
	                  10.11.6 15G31
	CPU: amd64
	     family 6 model 70 stepping 1
	     8 CPUs
	
	GPU: UNKNOWN
	
	Crash reason:  EXC_BAD_ACCESS / EXC_I386_GPFLT
	Crash address: 0x100fe7014
	Process uptime: 22 seconds
	
	Thread 10 (crashed)
	 0  Google Chrome Framework!ChromeMain + 0xacf04
	    rax = 0x0000000000000ff0   rdx = 0x00ffffffffffffff
	    rcx = 0x00007fdb4b710ea8   rbx = 0x00007fdb4b623490
	    rsi = 0x0000000000000000   rdi = 0x00007fdb4b710eb0
	    rbp = 0x0000700003a319f0   rsp = 0x0000700003a319c0
	     r8 = 0x0000000000000000    r9 = 0x00007fdb4b6234b8
	    r10 = 0x00000000004e7c00   r11 = 0x00000000e77b201b
	    r12 = 0x0000000000011210   r13 = 0x00000000003fffc0
	    r14 = 0x0000000000011210   r15 = 0x0000000000000010
	    rip = 0x0000000100fe7014
	    Found by: given as instruction pointer in context
	 1  Google Chrome Framework!ChromeMain + 0xae8f1
	    rbx = 0x0000700003a31a48   rbp = 0x0000700003a31a30
	    rsp = 0x0000700003a31a00   r12 = 0x0000000000000000
	    r13 = 0x00007fdb4e2027f0   r14 = 0x0000000000000010
	    r15 = 0x0000000000000000   rip = 0x0000000100fe8a01
	    Found by: call frame info
	 2  Google Chrome Framework!ChromeMain + 0x2e5bd73
	    rbx = 0x0000700003a31a48   rbp = 0x0000700003a31aa0
	    rsp = 0x0000700003a31a40   r12 = 0x0000000000000000
	    r13 = 0x00007fdb4e2027f0   r14 = 0x00007fdb4c826600
	    r15 = 0x0000000000000010   rip = 0x0000000103d95e83
	    Found by: call frame info
	 3  Google Chrome Framework!ChromeMain + 0x2e6e32a
	    rbx = 0x0000000106557249   rbp = 0x0000700003a31ad0
	    rsp = 0x0000700003a31ab0   r12 = 0x0000000000000000
	    r13 = 0x00007fdb4e2027f0   r14 = 0x00007fdb4c826600
	    r15 = 0x00ff000000000000   rip = 0x0000000103da843a
	    Found by: call frame info
	 4  Google Chrome Framework!ChromeMain + 0x271c4ef
	    rbx = 0x0000700003a31b18   rbp = 0x0000700003a31af0
	    rsp = 0x0000700003a31ae0   r12 = 0x0000000000000000
	    r13 = 0x00007fdb4e2027f0   r14 = 0x0000000007ff8f00
	    r15 = 0x00007fdb4b765f80   rip = 0x00000001036565ff
	    Found by: call frame info
	 5  Google Chrome Framework!ChromeMain + 0x271a440
	    rbx = 0x00007fdb4e202701   rbp = 0x0000700003a31c80
	    rsp = 0x0000700003a31b00   r12 = 0x0000000000000000
	    r13 = 0x00007fdb4e2027f0   r14 = 0x0000000007ff8f00
	    r15 = 0x00007fdb4b765f80   rip = 0x0000000103654550
	    Found by: call frame info
	 6  Google Chrome Framework!ChromeMain + 0x271a010
	    rbx = 0x00007fdb4b6f0300   rbp = 0x0000700003a31d20
	    rsp = 0x0000700003a31c90   r12 = 0x00007fdb4e68d8e4
	    r13 = 0x00007fdb4e68d8d0   r14 = 0x00000001083e8b68
	    r15 = 0x00007fdb4b6e6440   rip = 0x0000000103654120
	    Found by: call frame info
	 7  Google Chrome Framework!ChromeMain + 0x275b0e6
	    rbx = 0x00007fdb4e68d870   rbp = 0x0000700003a31dc0
	    rsp = 0x0000700003a31d30   r12 = 0x00007fdb4b45baf0
	    r13 = 0x00007fdb4e68d870   r14 = 0x00000001083e8b68
	    r15 = 0x00007fdb4b45ba80   rip = 0x00000001036951f6
	    Found by: call frame info
	 8  Google Chrome Framework!ChromeMain + 0x4fc8ae0
	    rbx = 0x00007fdb4b45bab0   rbp = 0x0000700003a31e30
	    rsp = 0x0000700003a31dd0   r12 = 0x00007fdb4b45baf0
	    r13 = 0x00007fdb4e68d870   r14 = 0x0000700003a31dd0
	    r15 = 0x00007fdb4b45ba80   rip = 0x0000000105f02bf0
	    Found by: call frame info
	 9  Google Chrome Framework!ChromeMain + 0x4fc7caa
	    rbx = 0x0000000000000000   rbp = 0x0000700003a31e80
	    rsp = 0x0000700003a31e40   r12 = 0x00007fdb4b528e38
	    r13 = 0x00007fdb4b45ba80   r14 = 0x00007fdb4b515124
	    r15 = 0x00007fdb4b515120   rip = 0x0000000105f01dba
	    Found by: call frame info
	10  Google Chrome Framework!ChromeMain + 0x19358bd
	    rbx = 0x00007fdb4b528dd0   rbp = 0x0000700003a31ec0
	    rsp = 0x0000700003a31e90   r12 = 0x00000000000008ff
	    r13 = 0x0000000000006103   r14 = 0x00007fdb4b528df0
	    r15 = 0x0000700003a31e90   rip = 0x000000010286f9cd
	    Found by: call frame info
	11  Google Chrome Framework!ChromeMain + 0x19324c7
	    rbx = 0x0000700003a32000   rbp = 0x0000700003a31ef0
	    rsp = 0x0000700003a31ed0   r12 = 0x00000000000008ff
	    r13 = 0x0000000000006103   r14 = 0x00007fdb4b528dd0
	    r15 = 0x00007fdb4b4327b0   rip = 0x000000010286c5d7
	    Found by: call frame info
	12  libsystem_pthread.dylib + 0x399d
	    rbx = 0x0000700003a32000   rbp = 0x0000700003a31f10
	    rsp = 0x0000700003a31f00   r12 = 0x00000000000008ff
	    r13 = 0x0000000000006103   r14 = 0x00007fdb4b5280b0
	    r15 = 0x000000010286c580   rip = 0x00007fff8a43499d
	    Found by: call frame info
	13  libsystem_pthread.dylib + 0x391a
	    rbp = 0x0000700003a31f50   rsp = 0x0000700003a31f20
	    rip = 0x00007fff8a43491a
	    Found by: previous frame's frame pointer
	14  libsystem_pthread.dylib + 0x1351
	    rbp = 0x0000700003a31f78   rsp = 0x0000700003a31f60
	    rip = 0x00007fff8a432351
	    Found by: previous frame's frame pointer
	15  Google Chrome Framework!ChromeMain + 0x1932470
	    rsp = 0x0000700003a32030   rip = 0x000000010286c580
	    Found by: stack scanning

+nednguyen

Ulan: Could you please figure out how to symbolize the stack trace (or modify the infrastructure to make sure that it's symbolized in future failures)?

shrike@, does your CL disable stack trace symbolization on MacOS: https://codereview.chromium.org/1560183002 ?

If so, is there a way to enable symbolization with run-time flags? We would like to get proper stack trace for a flaky crash on perfbot.

+Emily: can you look into why the stack trace was not symbolized?

Ping. Seems still flaky.

And I think this should be pri-2?

Yes, sorry I missed this.  So it seems like we are unable to debug this issue because of the unsymbolized stack trace which is the same as this bug, crbug.com/636340.

Looking at the failures here it doesn't seem to provide us more information on the trace that isn't being symbolized.

The next step will be for me to test locally on my mac to see if I can replicate the problem and dig into the code to see why it isn't being symbolized.

(Opening this back up because the problem still exists.)

The crash no longer happens.