Android 9: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) in libNativeScript.so

[timdoege]

Environment

• CLI: 5.4.2
• Cross-platform modules: 5.4.3
• Android Runtime: 5.4.0
• Plugin(s):
  • nativescript-angular
  • nativescript-geocoding
  • nativescript-geolocation
  • nativescript-local-notifications
  • nativescript-localize
  • nativescript-localstorage
  • nativescript-plugin-firebase
  • nativescript-pulltorefresh
  • nativescript-secure-storage
  • nativescript-sqlite
  • nativescript-trace-raven
  • nativescript-windowed-modal
  • nativescript-appversion

"markingMode": "none" is activated.

Describe the bug
After our app went live in the Play Store a couple of days ago, the Google Play Consoles crash report shows a concerning high rate of crashes with the following details:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libNativeScript.so

The crash report just consists of

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> *myapppath* <<<

backtrace:
  #00  pc 0000000000ac3c48  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so
  #01  pc 0000000000ac4bf0  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so (_Unwind_RaiseException+112)
  #02  pc 0000000000ab5748  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so (__cxa_throw+112)
  #03  pc 000000000021bd08  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so
  #04  pc 0000000d6468afcd  <unknown>

I am unable to reproduce this on my two test devices (Samsung J6 and Nokia 6.1) and the 4 different emulator images I have, but the reports show that all crashes are on Android 9, and nearly half of the devices are Sony XZ3's.

These crashes do not show up in Firebase Crashlytics (others, much less frequent ones do).
Based on Sentry.io logs, I am unable to find any sessions for these devices, so my guess is that the app crashes on launch.

Is there a way to troubleshoot this or narrow it down somehow?

[adrian-branescu]

Environment

• CLI: 5.4.2

• Cross-platform modules: 5.4.3

• Android Runtime: 5.4.0

• Plugin(s):

  • nativescript-angular
  • nativescript-geocoding
  • nativescript-geolocation
  • nativescript-local-notifications
  • nativescript-localize
  • nativescript-localstorage
  • nativescript-plugin-firebase
  • nativescript-pulltorefresh
  • nativescript-secure-storage
  • nativescript-sqlite
  • nativescript-trace-raven
  • nativescript-windowed-modal
  • nativescript-appversion

"markingMode": "none" is activated.

Describe the bug
After our app went live in the Play Store a couple of days ago, the Google Play Consoles crash report shows a concerning high rate of crashes with the following details:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) libNativeScript.so

The crash report just consists of

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> *myapppath* <<<

backtrace:
  #00  pc 0000000000ac3c48  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so
  #01  pc 0000000000ac4bf0  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so (_Unwind_RaiseException+112)
  #02  pc 0000000000ab5748  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so (__cxa_throw+112)
  #03  pc 000000000021bd08  /data/app/*myapppath*-89qUP8SF5_m_kuzi8EJipw==/lib/arm64/libNativeScript.so
  #04  pc 0000000d6468afcd  <unknown>

I am unable to reproduce this on my two test devices (Samsung J6 and Nokia 6.1) and the 4 different emulator images I have, but the reports show that all crashes are on Android 9, and nearly half of the devices are Sony XZ3's.

These crashes do not show up in Firebase Crashlytics (others, much less frequent ones do).
Based on Sentry.io logs, I am unable to find any sessions for these devices, so my guess is that the app crashes on launch.

Is there a way to troubleshoot this or narrow it down somehow?

I can replicate this segmentation fault.

What is your pattern of communication between JS land and Java land?
I am interested if:
a) communication is only one way: JS functions that are using Java symbols.
-OR-
b) communication is both ways: a) + Java instance properties set in JS functions. You can set a JS callback on a Java instance property in order to "register" a listener for native events (from Java side you can then call the JS callback whenever you want to notify the JS side about an event).

To be more specific I am asking if you have a similar scenario like this one: #1366