sentry-native
sentry-native copied to clipboard
sentry__unwind_stack_libunwindstack SIGABRT
Description
The Google Play SDK console is reporting some sentry-android-ndk related crashes. Unfortunately there aren't a lot of details, but maybe the backtraces can provide some context.
- [ ] During build
- [x] During run-time
- [ ] When capturing a hard crash
Environment
- OS: Android
- Compiler: unknown
- CMake version and config: unknown
Log outputs
Backtrace 1
#00 pc 0x000000000004e574 /apex/com.android.runtime/lib64/bionic/libc.so (abort+180)
#01 pc 0x00000000000429e0 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::die()+8)
#02 pc 0x0000000000043088 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::ScopedErrorReport::~ScopedErrorReport()+32)
#03 pc 0x0000000000043154 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::reportHeaderCorruption(void*)+60)
#04 pc 0x00000000000446f4 /apex/com.android.runtime/lib64/bionic/libc.so (scudo::Allocator<scudo::AndroidConfig, &(scudo_malloc_postinit)>::deallocate(void*, scudo::Chunk::Origin, unsigned long, unsigned long)+332)
#05 pc 0x000000000007f754 /data/app/<redacted>/lib/arm64/libsentry.so (sentry__unwind_stack_libunwindstack+884)
#06 pc 0x000000000007f0c4 /data/app/<redacted>/lib/arm64/libsentry.so
#07 pc 0x000000000007eec0 /data/app/<redacted>/lib/arm64/libsentry.so
#08 pc 0x0000000000004db8 /system/bin/app_process64 (art::SignalChain::Handler(int, siginfo*, void*)+352)
#09 pc 0x0000000000000678 [vdso] (__kernel_rt_sigreturn)
at <private>
#11 pc 0x00000000000b0bd8 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64)
#12 pc 0x00000000000505d0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
Backtrace 2
#00 pc 0x00000000000799c8 /apex/com.android.runtime/lib64/bionic/libc.so (abort+168)
#01 pc 0x00000000000623e4 /apex/com.android.runtime/lib64/bionic/libc.so (ifree+476)
#02 pc 0x00000000000626bc /apex/com.android.runtime/lib64/bionic/libc.so (je_free+120)
#03 pc 0x000000000007f780 /data/app/<redacted>lib/arm64/libsentry.so (sentry__unwind_stack_libunwindstack+928)
#04 pc 0x000000000007f0c4 /data/app/<redacted>lib/arm64/libsentry.so
#05 pc 0x000000000007eec0 /data/app/<redacted>lib/arm64/libsentry.so
#06 pc 0x0000000000000638 [vdso] (__kernel_rt_sigreturn)
#07 pc 0x00000000000799c4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164)
#08 pc 0x00000000000623e4 /apex/com.android.runtime/lib64/bionic/libc.so (ifree+476)
#09 pc 0x00000000000626bc /apex/com.android.runtime/lib64/bionic/libc.so (je_free+120)
at <private>
#11 pc 0x00000000000deb44 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264)
#12 pc 0x000000000007b2fc /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+68)
@supervacuus this relates to our recent discussion
this still happens from time to time . please see this event https://peerplay-ltd.sentry.io/discover/merge-cruise:da761de403254007cdddfbf584235d85/?field=title&field=event.type&field=project&field=user.display&field=timestamp&field=replayId&homepage=true&name=All+Events&project=4505424557375488&query=release.version%3A0.23.2&sort=-timestamp&statsPeriod=1h&yAxis=count%28%29
Hi, @matanplay. This looks very similar to other crashes we currently see on Android with recent upgrades to the OS (see https://github.com/getsentry/sentry-java/issues/2955). We are working with the Google ART team to determine the cause of these crashes. It is unclear if the crashes in this issue are related, but we're trying to find out.
Hi Mischan. The issue I have is actually very similar to this open bug you have in your repository https://github.com/getsentry/sentry-unity/issues/1469 ive recently also added some of my findings regarding the issue. so indeed I am anxious to get a fix for this. Please understand that this issue was the root cause of not only poor performance on our android games (the performance of our iOS games is top level on the hand) but we had to stop all marketing activities for a month, which is the time we spent finding the root cause and trying different ways to avoid it. This issue had a direct negative impact on our business. We do believe in Sentry as a Product and we value the service you provide. but at the end of the day, if this issue isn't resolved very soon I will have no choice but to uninstall the plugin and find other monitoring providers. we can't afford to be "blind" to our customers that are downloading our android games. also, i believe that we deserve some manner of compensation for the harsh business impact
Thank you for listening.
On Thu, Nov 9, 2023 at 4:41 PM Mischan Toosarani-Hausberger < @.***> wrote:
Hi, @matanplay https://github.com/matanplay. This looks very similar to other crashes we currently see on Android with recent upgrades to the OS (see getsentry/sentry-java#2955 https://github.com/getsentry/sentry-java/issues/2955). We are working with the Google ART team to determine the cause of these crashes. It is unclear if the crashes in this issue are related, but we're trying to find out.
— Reply to this email directly, view it on GitHub https://github.com/getsentry/sentry-native/issues/802#issuecomment-1803959852, or unsubscribe https://github.com/notifications/unsubscribe-auth/A6JCLVN7S6HZ6FI4CMMZPWLYDTTRHAVCNFSM6AAAAAAUTTUVPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBTHE2TSOBVGI . You are receiving this because you were mentioned.Message ID: @.***>
Hi @matanplay, thank you for writing in and providing data points on https://github.com/getsentry/sentry-unity/issues/1469 - we appreciate it and I provided a small update there.
Closing as the underlying issue has been resolved, see https://github.com/getsentry/sentry-native/pull/901#issuecomment-1938964058 for more details