art::StackVisitor::WalkStack<T>

[AndreasDev3]

Description

OS Version: Android 10 (VOG-L29 10.1.0.150(C431E19R2P5))
Report Version: 104

Exception Type: Unknown (SIGSEGV)

Application Specific Information:
Segfault

Thread 0 Crashed:
0   <unknown>                       0x75b68773d4        <unknown>

EOF

I am experiencing frequent fatal SIGSEGV crashes on Android that are not being symbolicated in Sentry. The crash reports only provide a minimal, non-descriptive stack trace with frames. This is occurring across multiple scenarios within the app, and there are no clear breadcrumbs to indicate a single cause. This occurs on pretty much all possible Android versions and I am using Sentry 5.11.0

All symbols have been uploaded for the release build as well.

[linear]

NET-429 art::StackVisitor::WalkStack<T>

[bruno-garcia]

@AndreasDev3 can you reproduce this problem consistently?
If so, could you run this .apk on that device, it might be able to give at least a bit more information, since it'll have some of the system images available for symbolication.

But that won't help much to be clear, seems like a crash in ART (Android Runtime) and we don't have debug symbols for that because Android manufacturers don't provide these.

I have one of those for Symbol Collector Android itself which runs on a device farm, and I didn't figure out what to do with it yet.
Lets see if our Android experts at Sentry have some tips.

[oferRounds]

expereincing this one also, have you been able to figure out more info about it?
@bruno-garcia – can you please provide instructions of how to use the symbol collector? couldn’t find any in repo itself

[jamescrosswell]

@oferRounds you can suppress these:

        var builder = MauiApp.CreateBuilder()
            .UseMauiApp<App>()
            .UseSentry(options =>
            {
                // All the standard options

#if ANDROID
                // Suppress native SIGSEGV Segfault errors
                options.Android.SuppressSegfaults = true;
#endif
            })

Per the advice in the docs for that option though:

Enabling this may prevent the capture of Segfault originating from native (not managed) code... so it may prevent the capture of genuine native Segfault errors.

@jpnurmi I think you found a more robust solution for this right?

[oferRounds]

Thank you @jamescrosswell! Where do you add this? And isn’t it only suppress the report on Sentry? Because our user’s app crashes

Also, adding to that we’re actually using React Native, so we’re on Sentry’s React Native

[jamescrosswell]

Also, adding to that we’re actually using React Native, so we’re on Sentry’s React Native

Aha... in that case the above won't help you. Those options are only available in the .NET SDK. You'll want to raise an issue asking for advise in the react native repo instead.