sentry-react-native: What are these fatal Segfault errors with no users but many events.
OS:
- Windows
- MacOS
- Linux
Platform:
- iOS
- Android
SDK:
-
@sentry/react-native(>= 1.0.0) -
react-native-sentry(<= 0.43.2)
SDK version:^1.7.1
react-native version: 0.61.2
Are you using Expo?
- Yes
- No
Are you using sentry.io or on-premise?
- sentry.io (SaaS)
- on-premise
If you are using sentry.io, please post a link to your issue so we can take a look:
Link to issue : https://sentry.io/organizations/ekeekaran-ventures/issues/1581216965/
Configuration:
(@sentry/react-native)
Sentry.init({
dsn: 'https://...@sentry.io/...'
// other options
});
I have the following issue:
I am having some unknown Segfault errors, which are actually shown as fatal, also there isn’t any stack trace shown. In my recent deployed app version, I have 87 events and 0 users. this looks really weird. how events are possible without users being registered to those events.
Expected result:
There should be actual users along with events and proper stack trace, which can help debug the issue.
Attaching the screenshot :
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 9
- Comments: 18 (8 by maintainers)
same issue, no user + crash gets reported in sentry and playstore
@GiorgioBertolotti indeed,
libjscisn’t part of the Sentry RN SDK so we can’t do much about it, thanks for letting us know.if you want the
libjscevents symbolicated by Sentry, you have to find out where it comes from and find its debug symbols as well and upload them to Sentry usingsentry-clihttps://docs.sentry.io/product/cli/dif/#uploading-filesHello @marandaneto, FYI I’m still facing this issue, with ~1.5k events on ~900 users. Just wanted to let you know that probably it’s still an issue, but for what I’ve read in this thread it may be related to a JavaScript crash, so honestly I don’t know what you can do about it.
~Hi @marandaneto, where exactly would one set
uploadNativeSymbols- I couldn’t find it while browsing the linked documentation, thanks in advance~Sorry, nevermind, I found it in the proguard settings: https://docs.sentry.io/platforms/android/proguard/#gradle-configuration
Thanks 🙇🏿
This looks like the JavaScriptCore crash that we are discussing here: https://github.com/facebook/react-native/issues/25494
Basically, it’s a bug deep in the JavaScript runtime environment. It’s not showing as much metadata as crash reports from JavaScript code, because it takes place much deeper in the software stack.
See the issue I linked for more info and partial solutions. Some people have luck with this patched version of JSC: https://github.com/facebook/react-native/issues/25494#issuecomment-567855193 and others have better luck if they switch to the Hermes runtime. We haven’t found a 100% solution yet.
cc @Swatinem