sentry crash by [sentry_get_modules_list]

Platform:

• Android -> min_sdk = 21 target_sdk = 30 build_tools = “30.0.2”

• Java -> JavaVersion.VERSION_1_8

• Kotlin -> 1.5.0

• NDK -> 21.3.6528143

IDE:

• Android Studio -> 4.2.1

Build system:

• Gradle -> 6.5.1

Android Gradle Plugin:

• Yes -> com.android.tools.build:gradle:4.0.1

Sentry Android Gradle Plugin:

• Yes -> 2.0.0

Proguard/R8:

• Enabled

Platform installed with:

• Maven Central

The version of the SDK: 5.0.1

---

I have the following issue:

sentry native crash from sentry dashboard issue, original crash info as follow:

OS Version: Android 10 (NOP-AN01P 2.0.0.116(C786E115R6P2))
Report Version: 104

Exception Type: Unknown (SIGSEGV)

Application Specific Information:
Segfault

Thread 0 Crashed:
0   libsentry.so                    0xc04c6adc          sentry_get_modules_list
1   libsentry.so                    0xc04c24d7          <unknown> + 3226215639
2   libsentry.so                    0xc04bf8dd          <unknown> + 3226204381
3   libsentry.so                    0xc04c70b7          <unknown> + 3226235063
4   libsentry.so                    0xc04c6ecd          <unknown> + 3226234573
5   libc.so                         0xf268ea90          <unknown> + 4066962064
6   libc.so                         0xf26944fe          abort
7   liblog.so                       0xef6edb2f          __android_log_assert
8   libandroid_runtime.so           0xf065fe33          android::bitmap::toBitmap
9   libandroid_runtime.so           0xf062037b          <unknown> + 4032955259
10  boot-framework.oat              0x7098e181          <unknown> + 1889067393



EOF

sentry gradle plugin config :

sentry {

    autoUpload = true

    uploadNativeSymbols = true

    includeNativeSources = false
}

more crash info：

Steps to reproduce:

• None

Actual result:

• Actual

Expected result:

• Result

[Abbondanzo]

It looks like this was fixed in #1651

[marandaneto]

Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated. There’s a large chance that this issue has been solved since. Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it. Cheers!