Describe the bug
We hit a tab freeze where a tween’s _prevRep points to itself, causing an infinite loop during update traversal. This was caused by a race condition in our app that started overlapping “replace” tweens on the same target/property. But it seems like the engine should be robust to re‑adding an already‑linked node so we're reporting.
Observed state in devtools:
// same ID repeating thousands of times
{ id: 5184, _prevRep: { id: 5184, ... } }`
Expected behavior
addChild should guard against re‑adding a node already linked in the list. Relevant call site
Provide a minimal reproduction demo of the bug
Inherently difficult, as this was caused by a bug in our own code that presented intermittently. It had to do with the interplay of animation promise landing, document.hidden foregrounding, and some state being tied to React render cycle. We fully acknowledge that part and just wanted to surface the edge case.
Thanks!
Describe the bug
We hit a tab freeze where a tween’s
_prevReppoints to itself, causing an infinite loop during update traversal. This was caused by a race condition in our app that started overlapping “replace” tweens on the same target/property. But it seems like the engine should be robust to re‑adding an already‑linked node so we're reporting.Observed state in devtools:
Expected behavior
addChild should guard against re‑adding a node already linked in the list. Relevant call site
Provide a minimal reproduction demo of the bug
Inherently difficult, as this was caused by a bug in our own code that presented intermittently. It had to do with the interplay of animation promise landing, document.hidden foregrounding, and some state being tied to React render cycle. We fully acknowledge that part and just wanted to surface the edge case.
Thanks!