"Failed to dispatch window animation state change" crash occasionally on Android #7165
Labels
Resolution: Locked
This issue was locked by the bot.
Comments
|
What RN version you are using? Why I'm asking (not sure if is related). I had a somewhat similar issue with RNRF. During app startup if try to change before the initial render is completed app will crash. Ref here |
|
This is happening with a fairly recent version of RN, close to 0.24. |
|
Anyone have an idea for a workaround? Since there seems to be some kind of memory leak, is there a way we can manually call some kind of garbage collection? I need my app to be able to run all day, while it always crashes at best about every ~12 hours. |
|
Any news on this? I get this crash all the time, it happens randomly while navigating in the app. It feels like it gets worse with every newer react native version, currently using 0.28 and while the project grows. If I can provide some more info, please let me know how. |
|
Having the same issue! |
|
Any updates on this? It's a serious bug which occurs a lot of times in my app. 07-19 05:56:24.567 381 765 E CameraService: disconnect: Disconnect called on already disconnected client for device 0
07-19 05:56:24.567 381 765 E CameraService: binderDied: Java client's binder died, removing it from the list of active clients
07-19 05:56:24.664 1051 1243 I OpenGLRenderer: Initialized EGL, version 1.4
07-19 05:56:24.730 1051 1243 W EGL_emulation: eglSurfaceAttrib not implemented
07-19 05:56:24.730 1051 1243 W OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0xddd3e280, error=EGL_SUCCESS
07-19 05:56:24.990 687 1974 E Surface : getSlotFromBufferLocked: unknown buffer: 0xde383420
07-19 05:56:25.254 687 718 W AppOps : Finishing op nesting under-run: uid 1000 pkg android code 24 time=0 duration=0 nesting=0
07-19 05:56:25.331 687 2280 W InputMethodManagerService: Got RemoteException sending setActive(false) notification to pid 2977 uid 10060
07-19 05:56:25.736 687 718 W WindowAnimator: Failed to dispatch window animation state change.
07-19 05:56:25.736 687 718 W WindowAnimator: android.os.DeadObjectException
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.BinderProxy.transactNative(Native Method)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.BinderProxy.transact(Binder.java:503)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.view.IWindow$Stub$Proxy.onAnimationStopped(IWindow.java:534)
07-19 05:56:25.736 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.updateWindowsLocked(WindowAnimator.java:286)
07-19 05:56:25.736 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.animateLocked(WindowAnimator.java:678)
07-19 05:56:25.736 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.-wrap0(WindowAnimator.java)
07-19 05:56:25.736 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator$1.doFrame(WindowAnimator.java:123)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:856)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.view.Choreographer.doCallbacks(Choreographer.java:670)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.view.Choreographer.doFrame(Choreographer.java:603)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.Handler.handleCallback(Handler.java:739)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.Handler.dispatchMessage(Handler.java:95)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.Looper.loop(Looper.java:148)
07-19 05:56:25.736 687 718 W WindowAnimator: at android.os.HandlerThread.run(HandlerThread.java:61)
07-19 05:56:25.736 687 718 W WindowAnimator: at com.android.server.ServiceThread.run(ServiceThread.java:46)
07-19 05:56:25.742 687 718 W WindowAnimator: Failed to dispatch window animation state change.
07-19 05:56:25.742 687 718 W WindowAnimator: android.os.DeadObjectException
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.BinderProxy.transactNative(Native Method)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.BinderProxy.transact(Binder.java:503)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.view.IWindow$Stub$Proxy.onAnimationStopped(IWindow.java:534)
07-19 05:56:25.742 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.updateWindowsLocked(WindowAnimator.java:286)
07-19 05:56:25.742 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.animateLocked(WindowAnimator.java:678)
07-19 05:56:25.742 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator.-wrap0(WindowAnimator.java)
07-19 05:56:25.742 687 718 W WindowAnimator: at com.android.server.wm.WindowAnimator$1.doFrame(WindowAnimator.java:123)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:856)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.view.Choreographer.doCallbacks(Choreographer.java:670)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.view.Choreographer.doFrame(Choreographer.java:603)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:844)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.Handler.handleCallback(Handler.java:739)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.Handler.dispatchMessage(Handler.java:95)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.Looper.loop(Looper.java:148)
07-19 05:56:25.742 687 718 W WindowAnimator: at android.os.HandlerThread.run(HandlerThread.java:61)
07-19 05:56:25.742 687 718 W WindowAnimator: at com.android.server.ServiceThread.run(ServiceThread.java:46) |
|
Looks like this is only happening when running Android app in "dev" environment, but not in "production". Is there any way to see and change some dev environment settings, so I could try to enable/disable some things to see if that could maybe help? |
Getting this issue too. This happens to me on Genymotion with Hot Reload enabled, after it hot reloads after changing a stateless functional component: |
|
Seeing this issue a lot in conjunction with We have a reproducible case in https://github.com/FormidableLabs/victory-uiexplorer-native - just run the app in Genymotion or Android stock emulator, navigate to |
|
Hello all, any update on this issue ? |
|
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
|
Still happening... |
|
For me as well. Should be reopened. |
|
If this is still happening to anyone, please submit a new issue with more information. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is tough to reproduce, I haven't noticed any patterns that lead to the crash but I see it at least once a day. @jesseruder pointed out that it might be an Android bug and not necessarily related to react-native. Similar crash report here: #6760
Has anyone seen this on FB apps? cc @mkonicek
The text was updated successfully, but these errors were encountered: