Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault Crash #15235

Closed
AliSoftware opened this issue Aug 24, 2021 · 10 comments · Fixed by #20911
Closed

Segfault Crash #15235

AliSoftware opened this issue Aug 24, 2021 · 10 comments · Fixed by #20911

Comments

@AliSoftware
Copy link
Contributor

AliSoftware commented Aug 24, 2021

Sentry Url: https://sentry.io/share/issue/ab1e2ab600d540aa964a361d54a1dd5d/
User Count: 582
Count: 1431
First Release: 17.7-rc-2
First Seen: 2021-07-04T09:26:28.771000Z
Last Seen: 2021-08-24T09:24:50Z
24 Hours: 24
30 Days: 1234

null: Segfault

Saw this one on Sentry today, quite an obscure one with not much data nor stacktrace to help 😒 … but seems the events are still steadily happening and building up since 17.7, so figured it could be worth tracking and checking.

@ravishanker
Copy link
Contributor

ravishanker commented Aug 25, 2021

It is hard to reproduce issue. Need to monitor and investigate further.

Most likely suspect is a null pointer dereference. Possibly in parsing a Gson somewhere using Java classes

@fluiddot
Copy link
Contributor

Not sure if the original issue was related to the Sentry library but I recently noticed that the stacktrace references the method sentry_get_modules_list which is defined by Sentry.

I looked for opened/closed issues on the Sentry repository (getsentry/sentry-java) that might be related and found this one with a similar problem. It states that the crash was addressed in version 5.1.0 by bumping sentry-native to 0.4.12. The current Sentry version defined in Automattic-Tracks-Android is 5.0.1, so I'm wondering if bumping Sentry to version 5.1.0 or newer might help.

@fluiddot
Copy link
Contributor

I see a reference to Hermes (facebook::hermes::detail::hermesFatalErrorHandler) in a recent Sentry event, so potentially this crash could be related to React Native library. It might be a coincidence but, the first event was originated in version 17.7 which is also the one where the React Native upgrade to version 0.64 was released 🤔 .

Screenshot 2021-11-26 at 15 58 32

Screenshot 2021-11-26 at 15 58 38

@ParaskP7
Copy link
Contributor

image

FYI: It seems that this event has been spiking for the past 3 months. Maybe it is worth to investigate it again as part of groundskeeping, wdyt? 🤔

@ovitrif
Copy link
Contributor

ovitrif commented Aug 5, 2022

@thehenrybyrd Following up on the internal discussion (↗️ ref: pbArwn-52u-p2#comment-6335) we can see in the graph of the past 3 months that the Sentry event has indeed started to show a recent downturn, therefore we might consider re-evaluating its priority in the near future 👍 .

90daystrend

@thehenrybyrd
Copy link
Contributor

Thanks for following up on this and giving an update @ovitrif! As we're seeing a significant decrease, I'll lower the priority on this one to low.

@antonis
Copy link
Contributor

antonis commented Mar 22, 2024

The issue exists since version 17.7 and the crash rate remains low

@irfano
Copy link
Member

irfano commented May 29, 2024

This occurred 20 times on May 26 and became one of the top crashes.

@antonis
Copy link
Contributor

antonis commented May 29, 2024

This occurred 20 times on May 26 and became one of the top crashes.

Checking the events I think they are all from the same user running WordPress 19.2 on a SM-S908B
device
with Android 14 :(

@irfano irfano linked a pull request May 30, 2024 that will close this issue
12 tasks
@irfano
Copy link
Member

irfano commented May 30, 2024

Fixed by #20911

@irfano irfano closed this as completed May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants