App crash: `hermes::vm::HadesGC::EvacAcceptor<false>::acceptNullable(hermes::vm::PinnedHermesValue&) ()` about react-native-reanimated HOT 9 CLOSED

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?

from react-native-reanimated.

Dzień dobry @mrousavy , layout animations for fabric are still under review: #6055

from react-native-reanimated.

So you can either switch to Paper for the time being, or await next stable release 👍

from react-native-reanimated.

Ah gotcha, I wasn't sure if it was related to Layout Animations or not - thanks for the quick reply! :)

from react-native-reanimated.

Dzień dobry @mrousavy, I am a bit confused about this issue since layout animations should be a noop on the new architecture. From your description it seems that some of them were running?

from react-native-reanimated.

Yea I do have layout animations, but they are all noop (in my app they just jump to the target value immediately).

from react-native-reanimated.

Can you check if removing those layout animations fixes these issues?
I've been working on layout animations on a separate branch and I'm not sure how layout animations could be causing these problems

from react-native-reanimated.

The issue was caused by reanimated accessing the UI runtime from two threads at the same time. Usually this doesn't happen, because we use WithRuntimeDecorator to wrap our runtime calls with a mutex. Unfortunately, methods related to NativeState were not included in this decorator, allowing for concurrent runtime access. I opened a PR to RN, which should resolve this issue.

from react-native-reanimated.

nice investigation!

from react-native-reanimated.