-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Frequent ANR: __cxa_throw ANR triggered by slow operations in main thread #10527
Comments
|
Sad news guys: Downgrading from NS 8.7.0 to NS 8.6.2 did clean ALL ANRs. Crashlytics is now reporting 61% better fail rates... Now I'll try to discover which commit did this. |
We are experiencing the exact same issue. ANR rates increased massively when updating to 8.7.0. Going back to 8.6.2 without any code changes fixed the issue. We are also observing same behaviour on 8.8.x Also, we can confirm that the ANRs happen after a phone reboot. Any news or findings on this? This issue could become critical as Google marks apps with high ANRs with bad behaviour. Anything we could do help here? |
Same here, also experiencing increased ANR rates with 8.8.2 |
Can you share the package.json as well as the stacks. |
Our package.json looks like this:
We have mainly two types of ANRs in different variants that increased massively when going to version 8.7.x. Stack trace #1:
And strack trace #2:
The ANRs occur across a broad range of devices and Android versions. |
@resc-app does your app use any push notification framework? I've noticed that the Crashlytics ANRs roughly matches the date and impressions of a marketing campaign that sent out push notifications in our app. |
@mukaschultze yes - we are. we use Airship for push notifications. However, our ANRs seem to occur after reboot of the device. However, we will check for behavior after a push campaign has been sent. |
I was able to reproduce the issue on the emulator by adding a PIN and then running We are also using Airship here, I know that I've created a PR on the android runtime repo that fixed the two ANRs that I was able to reproduce: |
One more update from our end: We have removed |
Issue Description
Hey guys. Since the latest NS update (8.7.0), Crashlytics is reporting frequent ANRs probably from the system startup.
Should we take care of this?
Reproduction
Its only happening on Crashlytics reports. Not able to check locally.
Relevant log output (if applicable)
Environment
Dependencies
Please accept these terms
The text was updated successfully, but these errors were encountered: