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

Issue 793187 link

Starred by 2 users
Status: Fixed
Owner: ----
Closed: Jan 2018
Cc:
█ thoren@chromium.org
dsinclair@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: ----



Sign in to add a comment

[Restrict-View-Google] Fatal during ACT test

Reported by ruch...@samsung.com, Dec 8 2017 
Device name: SM-G965U

From "Settings > About Chrome"
Application version: 62.0.3202.84
Operating system: O-OS


Steps to reproduce:
(1) Run ACT for overnight aging test
(2) Observe while running ACT script
(3)

Expected result:
There should be no application crash.

Actual result:
com.samsung.android.messaging Application was crashed while running ACT

Comment 1 by ruch...@samsung.com, Dec 8 2017 

12-06 18:58:58.358 10049 11413 11413 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-06 18:58:58.358 10049 11413 11413 F DEBUG   : Build fingerprint: 'samsung/star2qltesq/star2qltesq:8.0.0/OPR1.170623.032/G965USQU0AQL4:user/release-keys'
12-06 18:58:58.358 10049 11413 11413 F DEBUG   : Revision: '11'
12-06 18:58:58.358 10049 11413 11413 F DEBUG   : ABI: 'arm64'
12-06 18:58:58.358 10049 11413 11413 F DEBUG   : pid: 17061, tid: 17061, name: droid.messaging  >>> com.samsung.android.messaging <<<
12-06 18:58:58.358 10049 11413 11413 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
12-06 18:58:58.360 10049 11413 11413 F DEBUG   : Abort message: '[FATAL:gpu_info_collector_android.cc(184)] failed to create a temporary context for fetching driver strings. EGL_BAD_ALLOC (3003)
12-06 18:58:58.360 10049 11413 11413 F DEBUG   : '
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x0   0000000000000000  x1   00000000000042a5  x2   0000000000000006  x3   0000000000000008
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x4   6e716761ff083963  x5   6e716761ff083963  x6   6e716761ff083963  x7   7f7f7f7f7f7f7f7f
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x8   0000000000000083  x9   4771be3ba8bc9f46  x10  0000000000000000  x11  0000000000000001
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x12  ffffffffffffffff  x13  0000007fce715776  x14  000000718fe3a5a4  x15  0000000000000054
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x16  00000071a66dd2e8  x17  00000071a667eba0  x18  0000000000000009  x19  00000000000042a5
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x20  00000000000042a5  x21  00000071a66df808  x22  000000719068a000  x23  00000071a9d76a60
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x24  0000000000000001  x25  00000071a7b53170  x26  0000000000000000  x27  00000071a7b523c8
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     x28  00000071a7b53170  x29  0000007fce7157f0  x30  00000071a66312a4
12-06 18:58:58.360 10049 11413 11413 F DEBUG   :     sp   0000007fce7157b0  pc   00000071a667eba8  pstate 0000000060000000
12-06 18:58:58.361 radio  9091  9499 D TP/MmsProvider: query uri=content://mms/266/addr, match=13, calling pid = 17084
12-06 18:58:58.362 radio  9091  9499 D TP/MmsProvider: query uri=content://mms/266/addr, match=13:Elapsed time : 0.808 ms
12-06 18:58:58.362 10049 11413 11413 F DEBUG   : 
12-06 18:58:58.362 10049 11413 11413 F DEBUG   : backtrace:
12-06 18:58:58.362 10049 11413 11413 F DEBUG   :     #00 pc 000000000006bba8  /system/lib64/libc.so (tgkill+8)
12-06 18:58:58.362 10049 11413 11413 F DEBUG   :     #01 pc 000000000001e2a0  /system/lib64/libc.so (abort+88)
12-06 18:58:58.362 10049 11413 11413 F DEBUG   :     #02 pc 00000000007733a0  /system/app/Chrome/Chrome.apk (offset 0xbed000)

Comment 2 by shiva...@samsung.com, Dec 8 2017

CP_Intensive_Phone.txt
20.6 KB View Download
CRASH_com.samsung.android.messaging_20171206_185927.zip
8.9 MB Download

Comment 3 Deleted

Comment 4 by dtapu...@chromium.org, Jan 23 2018

Components: Internals>GPU>Internals

Comment 6 by piman@chromium.org, Jan 26 2018

Cc: thoren@chromium.org
Status: Fixed (was: Unconfirmed)
Sounds like a driver issue if we can't create contexts.

In any case, this was changed to a LOG(ERROR).
►

Sign in to add a comment