fix: guard against use-after-dispose in effect cleanups

When deps change, useDisposableMemo disposes the old property during
render, but the useEffect cleanup for that property runs later. Wrap
removeListener/removeListeners calls in try-catch since native dispose()
already handles listener cleanup. Also protect render-phase cleanup in
useDisposableMemo against throws.

Author: mfazekas

src/hooks/useDisposableMemo.ts

@@ -70,7 +70,11 @@ export function useDisposableMemo<T>(
       ref.current.pendingDisposal = null;
     }
     if (ref.current.deps !== UNINITIALIZED) {
-      cleanupRef.current(ref.current.value);
+      try {
+        cleanupRef.current(ref.current.value);
+      } catch {
+        // Swallow cleanup errors — the old value is being replaced regardless.
+      }
     }
     ref.current = { value: factory(), deps, pendingDisposal: null };
   }

src/hooks/useRiveList.ts

@@ -48,8 +48,13 @@ export function useRiveList(
     });
 
     return () => {
-      removeListener();
-      property.removeListeners();
+      try {
+        removeListener();
+        property.removeListeners();
+      } catch {
+        // Property may already be disposed by useDisposableMemo (deps change).
+        // Native dispose() handles listener cleanup, so this is safe to ignore.
+      }
     };
   }, [property]);
 

src/hooks/useRiveProperty.ts

@@ -86,7 +86,12 @@ export function useRiveProperty<P extends ViewModelProperty, T>(
         });
 
     return () => {
-      removeListener();
+      try {
+        removeListener();
+      } catch {
+        // Property may already be disposed by useDisposableMemo (deps change).
+        // Native dispose() handles listener cleanup, so this is safe to ignore.
+      }
     };
   }, [options, property]);