Significant increase of "SIGABRT: Abort" after updating to 5.3.0

[cmorigaki]

Gradle Version

8.11.1

AGP Version

8.6.1

Code Minifier/Optimizer

R8

Version

5.3.0

Sentry SDK Version

8.3.0

Steps to Reproduce

After updating Sentry plugin and SDK, we noticed on production an expressive increase of the "SIGABRT: Abort" crashes during the initial rollout of the new version. We reverted the changes and it came back to the normal levels. The crash is captured by the sentry.native.android sdk

Sentry Android Gradle Plugin: from 4.12.0 to 5.3.0
Sentry SDK Version: from 7.16.0 to 8.3.0

Expected Result

Same frequency of "SIGABRT: Abort" crashes of even no crashes of this type.

Actual Result

Before updating: 0,002% of the sessions impacted (2k/91M)
After updating: 0,194% of the sessions impacted (217/112k)

Stacktrace example. Most of them seems to be similar to this:

OS Version: Android 13 (TKQ1.221114.001 test-keys)
Report Version: 104

Exception Type: Unknown (SIGABRT)

Application Specific Information:
Abort

Thread 0 Crashed:
0   libc.so                         0x7c2e506774        abort
1   libc.so                         0x7c2e56eba0        <unknown> + 533353393056
2   libc.so                         0x7c2e56eab8        <unknown> + 533353392824
3   libc.so                         0x7c2e56e878        pthread_getcpuclockid
4   libart.so                       0x7ba0898c8c        art::Thread::GetCpuMicroTime
5   libart.so                       0x7ba089898c        <unknown> + 530974345612
6   libart.so                       0x7ba0898564        <unknown> + 530974344548
7   libc.so                         0x7c2e56e5c8        <unknown> + 533353391560
8   libc.so                         0x7c2e507fbc        <unknown> + 533352972220

Most of the impacted devices were running Android 13:

Another information that may be relevant is that we use DexProtector RASP solution.

[markushi]

@cmorigaki thanks for reaching out! Could you share a few more details about your SDK config? Which features (e.g. tracing, profiling, ...) are you using?

[cmorigaki]

thanks for your quick reply @markushi. Here is our configuration:

gradle sentry task configuration:

• includeProguardMapping = true
• autoUploadProguardMapping = true
• uploadNativeSymbols = true
• autoUploadNativeSymbols = true
• includeNativeSources = true
• includeSourceContext = true
• tracingInstrumentation.enabled = false
• autoInstallation.enabled = false
• includeDependenciesReport = false
• telemetry = false

init configuration:

• tracesSampleRate = 0.005
• profilesSampleRate = 0.005
• idleTimeout = 1000L
• isEnableAutoActivityLifecycleTracing = true
• isEnableActivityLifecycleTracingAutoFinish = true
• isEnablePerformanceV2 = true

Also, we're using these packages:

• io.sentry:sentry-android:8.3.0
• io.sentry:sentry-android-fragment:8.3.0
• io.sentry:sentry-okhttp:8.3.0
• io.sentry:sentry-compose-android:8.3.0

[markushi]

@cmorigaki thanks for all the details! Could you double check and see if you changed any of the sample rates when upgrading the SDK version? Additionally could you check if your app is using any native libraries?

This sounds like a known issue which has been around for a while, where the Android system profiler crashes due to a native thread not being detached from the ART runtime correctly. See our docs https://docs.sentry.io/platforms/android/profiling/troubleshooting/#i-see-elevated-number-of-crashes-in-the-android-runtime-when-profiling-is-activated for more details.