DrRefactor

is someone working on it, or has any suggestions on how to approach it?

Hello, it does not happen on nightly build anymore. It was due to the way of how exiting animation was handled in 3.6.2: 1. true element was hidden via visibility:...

The fixing PR is here: https://github.com/software-mansion/react-native-reanimated/pull/5444

Please see repo readme on how to monitor memory usage conveniently.

My repro app started using 130MB, reaching 430MB after an hour.

Last ~30 minutes of logs from my `monitor-memory.sh` script: ``` [”15:57:55”]: peak memory: 252 253M 0:50.85 [”15:57:58”]: peak memory: 253 253M 0:51.06 [”15:58:01”]: peak memory: 253 254M 0:51.27 [”15:58:04”]: peak...

Started testing, will let you know in a while. I've had some problems to compile with nightly build, so I created PR with potential fix (just for an app build):...

It looks really promising, memory did rise up a bit, but GC's done its job after some time, and memory is kept in check since. It's been about 40 minutes,...

This commit seems to have fixed the issue: https://github.com/software-mansion/react-native-reanimated/commit/b7f5805c0108a04dc940dd0fb9ef88b951ac1b86

I have bad news @ranaavneet - I've extended my repo repro to use basic animation via useAnimatedStyle, and it leaks again, quite quickly. https://github.com/DrRefactor/reanimated-issue-5614-repro/blob/main/App.tsx