Today we get one of this crashes on our local machines.
This problem occur only on Galaxy S7 (herolte) and Galaxy S7 Edge (hero2lte). (about 18% our customer use this mobile phone)

Here is the compleat crash Log :

                                                                                                                  --------- beginning of crash
09-14 13:42:27.669 13232-13204/? A/google-breakpad: Microdump skipped (uninteresting)
09-14 13:42:27.693 12476-13204/de.eventim.mobile.app.Android W/google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
09-14 13:42:27.693 12476-13204/de.eventim.mobile.app.Android W/google-breakpad: Chrome build fingerprint:
09-14 13:42:27.693 12476-13204/de.eventim.mobile.app.Android W/google-breakpad: 3.0.381
09-14 13:42:27.693 12476-13204/de.eventim.mobile.app.Android W/google-breakpad: 3000381
09-14 13:42:27.693 12476-13204/de.eventim.mobile.app.Android W/google-breakpad: ### ### ### ### ### ### ### ### ### ### ### ### ###
09-14 13:42:27.694 12476-13204/de.eventim.mobile.app.Android A/libc: Fatal signal 11 (SIGSEGV), code 2, fault addr 0x73d0a7b000 in tid 13204 (ile.app.Android)
                                                                     
                                                                     [ 09-14 13:42:27.699  3095: 3095 W/         ]
                                                                     debuggerd: handling request: pid=12476 uid=10211 gid=10211 tid=13204
09-14 13:42:27.713 3815-3852/? D/LockSettingsStorage: mSKTLockState = 2
09-14 13:42:27.715 3815-3852/? D/LockSettingsStorage: mSKTLockState = 2
09-14 13:42:27.839 13234-13234/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-14 13:42:27.839 13234-13234/? A/DEBUG: Build fingerprint: 'samsung/heroltexx/herolte:7.0/NRD90M/G930FXXS1DQG4:user/release-keys'
09-14 13:42:27.839 13234-13234/? A/DEBUG: Revision: '8'
09-14 13:42:27.839 13234-13234/? A/DEBUG: ABI: 'arm64'
09-14 13:42:27.840 13234-13234/? A/DEBUG: pid: 12476, tid: 13204, name: ile.app.Android  >>> de.eventim.mobile.app.Android <<<
09-14 13:42:27.840 13234-13234/? A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x73d0a7b000
09-14 13:42:27.849 13234-13234/? A/DEBUG: Abort message: 'PRODUCTION: Adjust is running in Production mode. Use this setting only for the build that you want to publish. Set the environment to `sandbox` if you want to test your app!'
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x0   00000073d0a7adc0  x1   00000073d0a7ab54  x2   0000000000000030  x3   0000000000000028
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x4   0000000000000000  x5   0000000000000019  x6   000000000000000c  x7   0000000000000019
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x8   0000000000000000  x9   00000073d91e6690  x10  00000073d0a7a934  x11  00000073d0a7aff4
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x12  00000073d9d18db0  x13  ffffffffffffffd0  x14  0000000000000001  x15  00000073d0a7a904
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x16  00000073db523470  x17  00000073d9d1fef0  x18  00000073cb014d70  x19  00000073d0a7aff4
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x20  00000073cccca280  x21  000000000000001c  x22  00000073cb014d70  x23  000000000000000c
09-14 13:42:27.849 13234-13234/? A/DEBUG:     x24  0000000000000030  x25  000000000000000a  x26  000000000000000b  x27  00000073cccca280
09-14 13:42:27.850 13234-13234/? A/DEBUG:     x28  00000073cd0bc980  x29  00000073d91e6900  x30  00000073d9d1e994
09-14 13:42:27.850 13234-13234/? A/DEBUG:     sp   00000073d91e6640  pc   00000073d9d18db8  pstate 0000000080000000
09-14 13:42:27.852 13234-13234/? A/DEBUG: backtrace:
09-14 13:42:27.853 13234-13234/? A/DEBUG:     #00 pc 0000000000031db8  /system/lib64/libRSCpuRef.so
09-14 13:42:27.853 13234-13234/? A/DEBUG:     #01 pc 0000000000037990  /system/lib64/libRSCpuRef.so

Some similar crashes where chrome is involved :



Heute, 14:12 in der App-Version 3000381
Samsung Galaxy S7 (herolte), 4096MB RAM, Android 7.0

Bericht 1 von 4
backtrace:
 
  native: pc 000000000007f3bc  /system/lib64/libc.so (arena_avail_insert+120)
 
  native: pc 000000000007f314  /system/lib64/libc.so (arena_chunk_alloc+748)
 
  native: pc 000000000007a864  /system/lib64/libc.so (je_arena_malloc_large+148)
 
  native: pc 000000000008dd48  /system/lib64/libc.so (je_malloc+324)
 
  native: pc 00000000007e8cc4  /data/app/com.android.chrome-1/base.apk

Regards
Stephan

can you provide crash id from chrome://crashes?

Not at the moment in case we reproduce the problem I tell my colleague to add more information.
Regards
Stephan

Hi,

We're observing large amount of crashes for our app in "Android Vitals"-Crashes, with the following back trace (unfortunately no further data is available):

native: pc 0000000001c10fa8  /data/app/com.android.chrome-2/base.apk
native: pc 0000000001be0cd0  /data/app/com.android.chrome-2/base.apk

The problem mostly occurs on the following:
Devices: Galaxy S7 Edge, Galaxy S8, Galaxy S7 Galaxy S8+
OS:      Android 7.0, Android 7.1

Crashes: ~200-250 this week (~2% of sessions).

Have you noticed something like this recently?

Thanks,
Michael.

We use RenderScript to blur pictures.

Since the crashes are only on Samsung phones and this StackOverflow :

https://stackoverflow.com/questions/41976829/scriptintrinsicblur-broken-on-api-24-on-galaxy-s7/42196495#42196495

post we made the decision to blur the pictures not with RenderScript.

Since this changes the crash is gone. 
Regards
Stephan

@skseventim -- Could you please help us in providing Crash ID which would help us in triaging further.
Thanks in Advance.

Hi msrchandra
we have no Crash ID.
The problem incidence only with our customer. 
We only know about this from 'Google Play Store' cash entry.
Regards

Thank you for providing more feedback. Adding requester "msrchandra@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Do we have any update on these crashes? 

We removed the RenderScript blur from our application and blur the image in the CPU.... 
I know this is not a good solution but the only one we are able to do.

For more information about the Samsung bug contact 'Google Engineer'
see :

https://stackoverflow.com/questions/41976829/scriptintrinsicblur-broken-on-api-24-on-galaxy-s7/42196495#42196495

Regards

Closing this issue as there is no activity on this issue.

skseventim@ -- Please feel free to file a new issue if the issue is observed on the latest Chrome #64.0.3282.137 along with the Crash logs.

Thanks in advance!