The xr.webvr.live.static benchmark seems to have started flakily crashing a while back, particularly on the with.in sites. Unfortunately, the tests are run on builds that are as close to official builds as possible, meaning that we can't get a whole lot of useful information from the crashes. Additionally, trying to add logging to get more information seems to make the issue go away, as does changing to a debug build.
The following stack traces are from one of the runs on the bot:
[FATAL:jni_android.cc(259)] Please include Java exception stack in crash report
signal 6 (SIGABRT), code -6 in tid 6663 (chromium.chrome)
pid: 6663, tid: 6663, name: chromium.chrome >>> org.chromium.chrome <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
[FATAL:jni_android.cc(259)] Please include Java exception stack in crash report
r0 00000000 r1 00001a07 r2 00000006 r3 00000008
r4 f39e858c r5 00000006 r6 f39e8534 r7 0000010c
r8 ffd9970d r9 ffd9970c sl ffd99b68 fp ffd99b64
ip 0000000b sp ffd99698 lr f13b05c7 pc f13b2e30
Stack Trace:
RELADDR FUNCTION FILE:LINE
00049e30 <UNKNOWN> /system/lib/libc.so
000475c3 <UNKNOWN> /system/lib/libc.so
0001d635 <UNKNOWN> /system/lib/libc.so
00019181 <UNKNOWN> /system/lib/libc.so
00017048 <UNKNOWN> /system/lib/libc.so
0060dec7 base::debug::(anonymous namespace)::DebugBreak() ../../base/debug/debugger_posix.cc:228:5
Java stderr from crashing pid (may identify underlying Java exception):
java.lang.NullPointerException: Attempt to write to field 'int aui.h' on a null object reference
at auw.onLargeIconAvailable(PG:1128)
at org.chromium.base.SystemMessageHandler.nativeDoRunLoopOnce(Native Method)
at org.chromium.base.SystemMessageHandler.handleMessage(PG:51)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6121)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
Comment 1 by bugdroid1@chromium.org
, Mar 29 2018