When an animation value is updated from a clock, the clock delivers the notification on the main thread - and any derived values are updated on the javascript thread.

There is a race condition that we see in the new Path interpolating example if we remove the line in runTiming where we reset the value.animation to undefined in the callback, it crashes.

The reason is that when we are notified on the native thread and then dispatch an update on the JS thread there might be a situation where the object's destructor is called before the JS operation has finished. This will cause a crash.