SIGABRT - Native crash on Samsung devices running Android 12

Environment

• Android OS version: Android 12
• Devices affected: Only Samsung devices (SM-S908U, SM-G996U, SM-S901U, SM-N986U, SM-F711U, SM-F936U, ...)
• Maps SDK Version: 10.7.0, 10.8.0

Observed behavior and steps to reproduce

• We could not reproduce the crash but we can see the analytics events fired before the crash:
• 1. User launches the app. The initial screen is a fragment with a MapView.
• 2. The crash happens either at the app launch (before the fragment with MapView is loaded) or right after the fragment is loaded.

SIGABRT Abort program /apex/com.android.runtime/lib64/bionic/libc.so:334716 abort /apex/com.android.runtime/lib64/bionic/libc.so:267876 scudo::die() /apex/com.android.runtime/lib64/bionic/libc.so:269692 scudo::ScopedErrorReport::~ScopedErrorReport() /apex/com.android.runtime/lib64/bionic/libc.so:270288 scudo::reportInvalidChunkState(scudo::AllocatorAction, void*) /apex/com.android.runtime/lib64/bionic/libc.so:276076 scudo::Allocator<scudo::AndroidConfig, &scudo_malloc_postinit>::deallocate(void*, scudo::Chunk::Origin, unsigned long, unsigned long) /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3049648 0x7949f238b0 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3053908 0x7949f24954 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3046420 0x7949f22c14 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3042340 0x7949f21c24 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3040696 0x7949f215b8 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:3010112 0x7949f19e40 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:2688456 0x7949ecb5c8 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/split_config.arm64_v8a.apk!/lib/arm64-v8a/libmapbox-maps.so:2301556 0x7949e6ce74 /data/app/~~_2--0h93ACPR9pHhIGV-6w==/com.example.app-ZtmHjD0tXEcUUikBUwc_FQ==/oat/arm64/base.odex:2831344 art_jni_trampoline

Expected behavior

The app should not crash after being launched.

Notes / preliminary analysis

This is currently our top crash in the app.

Additional links and references

Inizia con lo stack trace di SIGABRT in libmapbox-maps.so e con il percorso di avvio dell’app che coinvolge il fragment MapView iniziale. Verifica se il crash è riproducibile sui dispositivi Samsung elencati con Android 12 e Maps SDK 10.7.0 o 10.8.0; il lavoro è completato quando il crash dell’allocatore nativo è stato identificato e risolto, in modo che l’app venga avviata senza abortire.