signal 11 (SIGSEGV) crash with realm 2.28.0 on some Android devices

[yenda]

Goals

Get the app to start with realm 2.28

Expected Results

The app runs fine like it did with 2.26

Actual Results

06-06 12:12:13.021  2699  2699 I Timeline: Timeline: Activity_idle id: android.os.BinderProxy@e6de52c time:10308307
06-06 12:12:13.071  3064  3064 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-06 12:12:13.071  3064  3064 F DEBUG   : Build fingerprint: 'samsung/zerofltexx/zeroflte:6.0.1/MMB29K/G920FXXU5DQA8:user/release-keys'
06-06 12:12:13.071  3064  3064 F DEBUG   : Revision: '11'
06-06 12:12:13.071  3064  3064 F DEBUG   : ABI: 'arm'
06-06 12:12:13.071  3064  3064 F DEBUG   : pid: 2699, tid: 2749, name: mqt_js  >>> im.status.ethereum.pr <<<
06-06 12:12:13.071  3064  3064 F DEBUG   : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x460eb084
06-06 12:12:13.081  3064  3064 F DEBUG   :     r0 00000000  r1 00000000  r2 46d525e2  r3 460eb084
06-06 12:12:13.081  3064  3064 F DEBUG   :     r4 d8031b88  r5 00000000  r6 d5b623ac  r7 d5b62300
06-06 12:12:13.081  3064  3064 F DEBUG   :     r8 eeb2f92c  r9 eebfe0f8  sl eeb2f924  fp f72d5ec0
06-06 12:12:13.081  3064  3064 F DEBUG   :     ip d8031d14  sp d5b622c0  lr d7b37538  pc 460eb084  cpsr 600e0010
06-06 12:12:13.081  3064  3064 F DEBUG   : 
06-06 12:12:13.081  3064  3064 F DEBUG   : backtrace:
06-06 12:12:13.081  3064  3064 F DEBUG   :     #00 pc 134ea084  /dev/ashmem/dalvik-main space 1 (deleted) (offset 0x1000)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #01 pc 0021b534  /data/app/im.status.ethereum.pr-1/lib/arm/librealmreact.so
06-06 12:12:13.081  3064  3064 F DEBUG   :     #02 pc 0002063d  /data/app/im.status.ethereum.pr-1/lib/arm/libjscexecutor.so (_ZN8facebook3jsc10JSCRuntimeC1Ev+16)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #03 pc 0002264b  /data/app/im.status.ethereum.pr-1/lib/arm/libjscexecutor.so (_ZN8facebook3jsc14makeJSCRuntimeEv+14)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #04 pc 00018c0f  /data/app/im.status.ethereum.pr-1/lib/arm/libjscexecutor.so
06-06 12:12:13.081  3064  3064 F DEBUG   :     #05 pc 000a56f3  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so (_ZN8facebook5react16NativeToJsBridgeC1EPNS0_17JSExecutorFactoryENSt6__ndk110shared_ptrINS0_14ModuleRegistryEEENS5_INS0_18MessageQueueThreadEEENS5_INS0_16InstanceCallbackEEE+146)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #06 pc 000a0913  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so
06-06 12:12:13.081  3064  3064 F DEBUG   :     #07 pc 000867df  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so
06-06 12:12:13.081  3064  3064 F DEBUG   :     #08 pc 0008531b  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so
06-06 12:12:13.081  3064  3064 F DEBUG   :     #09 pc 000791af  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so (_ZN8facebook3jni6detail13MethodWrapperIMNS_5react15JNativeRunnableEFvvEXadL_ZNS4_3runEvEES4_vJEE8dispatchENS0_9alias_refIPNS1_8JTypeForINS0_11HybridClassIS4_NS3_8RunnableEE8JavaPartESB_vE11_javaobjectEEE+10)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #10 pc 000791e9  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so (_ZN8facebook3jni6detail17WrapForVoidReturnIPFvNS0_9alias_refIPNS1_8JTypeForINS0_11HybridClassINS_5react15JNativeRunnableENS6_8RunnableEE8JavaPartES8_vE11_javaobjectEEEEXadL_ZNS1_13MethodWrapperIMS7_FvvEXadL_ZNS7_3runEvEES7_vJEE8dispatchESE_EEvJSD_EE4callEOSD_+20)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #11 pc 0007915f  /data/app/im.status.ethereum.pr-1/lib/arm/libreactnativejni.so (_ZN8facebook3jni6detail15FunctionWrapperIPFvNS0_9alias_refIPNS1_8JTypeForINS0_11HybridClassINS_5react15JNativeRunnableENS6_8RunnableEE8JavaPartES8_vE11_javaobjectEEEEXadL_ZNS1_13MethodWrapperIMS7_FvvEXadL_ZNS7_3runEvEES7_vJEE8dispatchESE_EESD_vJEE4callEP7_JNIEnvP8_jobject+30)
06-06 12:12:13.081  3064  3064 F DEBUG   :     #12 pc 015ef937  /data/app/im.status.ethereum.pr-1/oat/arm/base.odex (offset 0x13e4000)
06-06 12:12:13.281  3064  3064 F DEBUG   : 
06-06 12:12:13.281  3064  3064 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_00
06-06 12:12:13.281  3064  3064 E DEBUG   : AM write failed: Broken pipe
06-06 12:12:13.281  3064  3064 E         : ro.product_ship = true
06-06 12:12:13.281  3064  3064 E         : ro.debug_level = 0x4f4c
06-06 12:12:13.281  3064  3064 E         : sys.mobilecare.preload = false
06-06 12:12:13.281  3501  2751 D FocusedStackFrame: Set to : 0
06-06 12:12:13.281  5678  5678 E audit   : type=1701 msg=audit(1559815933.281:356): auid=4294967295 uid=10467 gid=10467 ses=4294967295 subj=u:r:untrusted_app:s0:c512,c768 pid=2749 comm="mqt_js" reason="memory violation" sig=11

Steps to Reproduce

Run https://status.im/nightly/ on one of the following devices:

Can reproduce issue

Galaxy S6, Android 6.0.1
Galaxy S7, Android 6
Galaxy S7, Android 8.0.0
Galaxy S8, Android 7
Can't reproduce issue:

Galaxy Note 4, Android 6.0.1
Nexus 6, Android 6

Code Sample

https://github.com/status-im/status-react

Version of Realm and Tooling

• Realm JS SDK Version: 2.28.0
• Node or React Native: 0.59.2
• Client OS & Version: Android 6 7 8
• Which debugger for React Native: None

[yenda]

On our side we are trying to exclude 64bits builds here status-im/status-mobile#8367 but it doesn't seem to be enough. So even though we are aware of the react-native issue here facebook/react-native#25060, we have never encountered it before the realm upgrade and it doesn't seem to be related to 64 bits apk but rather 64 bits procs in general with the latest version of realm?

[ThrowJojo]

Have you tried using v2.28.1? I think it solves most of these issues:

#2391 (comment)

[yenda]

@ThrowJojo it does thanks

[realm-probot]

Hey - looks like you forgot to add a T:* label - could you please add one?