ANR caused by performOperations #5884
Labels
Missing info
The user didn't precise the problem enough
Missing repro
This issue need minimum repro scenario
Platform: Android
This issue is specific to Android
Comments
|
Hey! 👋 The issue doesn't seem to contain a minimal reproduction. Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem? |
github-actions
bot
added
Missing repro
|
Hey! 👋 It looks like you've omitted a few important sections from the issue template. Please complete Snack or a link to a repository section. |
|
Happens to us too, but in our case sentry catched it: react-native: '0.73.7' |
|
@sabin10 Hi, have you found any fix for this? |
|
Getting the same issue: react-native: 0.73.6 |
|
I believe it should work with the latest version of Reanimated. |
|
@piaskowyk Did it got fixed in the latest version? Can you point me to the version that fixes this issue? |
|
Tried latest version 3.15.0 but issue is still there. |
|
Hi! It's seems to be related to this issue. It was caused by RN missing some methods in their |
Is this fix will work only with RN 0.76.0-rc.0+ ? |
|
We have 53%+ of ANRs in our app exactly with same errors: And this started to happening since end of march (when reanimated 3.7.0/3.8.0+ was released): With this version our app doesn't freeze: https://github.com/software-mansion/react-native-reanimated/releases/tag/3.6.3 
|
|
@kesha-antonov The fix should work in 0.75, because the included PR fixed the methods that were causing our issues (though it's worth checking if the other PR helps here). I am currently working on fixing another issue that looks similar. Could you post the entire stack trace, so I can figure out whether it's the new issue? Were you able to reproduce the bug, or do you only have these reports? |
We tried 0.75 but ANRs are still there (but less of them I think). Here's the most recent one ANR: Details |
|
Same here started after package update as described above |
|
Stacktrace from RN0.73 and Reanimated 3.15.0 |
|
Still happens on 0.76.5 and 3.16.5 |
|
This might be related to this hermes issue that recently got resolved. We should see after the next hermes release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We are seeing multiple ANRs with reanimated at the top of the stack trace. These are not showing in Sentry or Firebase Crashlytics, only in Play Store release which is now penalising our app.
Stack trace:
"main" tid=1 Timed Waiting
at java.lang.Object.wait (Native method)
at java.lang.Thread.parkFor$ (Thread.java:2153)
at sun.misc.Unsafe.park (Unsafe.java:358)
at java.util.concurrent.locks.LockSupport.parkNanos (LockSupport.java:230)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos (AbstractQueuedSynchronizer.java:1061)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos (AbstractQueuedSynchronizer.java:1352)
at java.util.concurrent.Semaphore.tryAcquire (Semaphore.java:415)
at com.swmansion.reanimated.NodesManager.performOperations (NodesManager.java:242)
at com.swmansion.reanimated.nativeProxy.NativeProxyCommon.maybeFlushUIUpdatesQueue (NativeProxyCommon.java:262)
at com.swmansion.reanimated.AndroidUIScheduler.triggerUI (Native method)
at com.swmansion.reanimated.AndroidUIScheduler$1.run (AndroidUIScheduler.java:24)
at com.swmansion.reanimated.AndroidUIScheduler$2.runGuarded (AndroidUIScheduler.java:43)
at com.facebook.react.bridge.GuardedRunnable.run (GuardedRunnable.java:29)
at android.os.Handler.handleCallback (Handler.java:795)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:166)
at android.app.ActivityThread.main (ActivityThread.java:6861)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:450)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:936)
Other reports from Google Play:
Android versions affected: 11-7
Devices: HUAWEI HWDRA-MG, realme RMX2180, Redmi begonia, TCL HONG_KONG, etc
Steps to reproduce
There was a similar report previously: #2251. But the last comment here says that this should be fixed after v3. So maybe this is a regression? Other than that, it's hard to provide concrete steps to reproduce.
Reanimated version
3.6.2
React Native version
0.73.6
Platforms
Android
JavaScript runtime
Hermes
Workflow
Expo Dev Client
Architecture
Paper (Old Architecture)
Build type
Release app & production bundle
Device
Real device
Device model
HUAWEI HWDRA-MG, realme RMX2180, Redmi begonia, TCL HONG_KONG, etc.
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: