getsentry/sentry-react-native

Sentry is delaying react-navigation transition

buesing opened this issue ยท 13 comments

I was investigating react-navigation/react-navigation#608 and it looks like Sentry takes very long to parse an error during a transition. On a physical iPhone 6, it was delaying a transition by over 3 seconds. I found this by profiling with Instruments on macOS. Here's a screenshot of the stacktrace, where you can see that Sentry calls are blocking the transition for a long time. Removing Sentry from the app fixes the problem. I tried upgrading to the latest version, problem persists. Let me know if I can help with further details.

bildschirmfoto 2017-07-19 um 16 50 39

HazAT commented

Hey, thx for reporting this.
For now you can just disable the stacktrace merging which should resolve the performance issue.
deactivateStacktraceMerging: true
https://docs.sentry.io/clients/react-native/config/
We are currently looking into improving the performance so this does not happen at all.

I was having the same issue with react-navigation where I was experiencing a 1-2 second delay before transitioning to a new screen. After deactivating the stacktrace merging functionality in Sentry, the issue appears to be fixed.

Where exactly is Sentry I don't seem to have it in my project

I was having the same issue with react-navigation and sentry.

It's very smoothly in debug mode, bug so slow in release mode without any changes but sentry.

๐Ÿ˜ณ

Same here. Hope a fix will be available soon. It slows down so much that almost make the app unusable.

HazAT commented

Hey @huhuanming @willlaserlike,
Do you still have troubles when deactivating stacktrace merging?

@HazAT Deactivating stacktrace seems to fix it. But stacktrace merging is kind of the key reason I choose Sentry so I wanna have it back plz...

HazAT commented

@willlaserlike Are you running the latest version 0.20.0
We've released some performance improvements in the last few releases, I am still trying to reproduce this.
In the meantime, you could maybe upgrade to the latest version and try it again.

thx.
I will update and test it later.

HazAT commented

I've just released 0.22.0 which should fix the problem. Please try it out and tell me if it works.

Hi @HazAT - Can confirm it has fixed the issue for us in deployed versions ๐ŸŽ‰ thanks!