Sentry is delaying react-navigation transition

[buesing]

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.

[HazAT]

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.

[jordanmkoncz]

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.

[ChizuNoYama]

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

[huhuanming]

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.

[huhuanming]

😳

[willlaserlike]

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

[HazAT]

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

[willlaserlike]

@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]

@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.

[huhuanming]

thx.
I will update and test it later.

[plasticine]

Can confirm the issue persists with the latest `react-native-sentry` release. Fine in dev, slow transitions in release builds. Disabling stack trace merging seems to continue to resolve the issue as a temporary workaround for now.

…

On Sun, 27 Aug 2017 at 11:49 pm, huhuanming ***@***.***> wrote: thx. I will be update and test it later. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#158 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABGnEY1fBPiMOfAQwBeBzb3qAlCetKSks5scXPagaJpZM4Oc248> .

[HazAT]

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

[tommeier]

Hi @HazAT - Can confirm it has fixed the issue for us in deployed versions 🎉 thanks!