Chart.js 4.x Animation State Persistence with Zero-Duration Updates

Animation State Behavior During Rapid Data Updates

When using Chart.js 4.x with live data feeds, the interaction between animation configuration and rapid dataset updates presents an unresolved behavioral question. The documentation indicates that animation.duration can be set to 0, but the precise implications for animation state management during high-frequency updates remain unclear.

Research findings suggest that Chart.js 4.x preserves animation state across data updates when duration is set to 0, maintaining previous frame positions rather than resetting interpolation. However, the library does not automatically reset animation interpolation when new datasets replace existing ones without an explicit chart.update() call, potentially leading to unexpected visual artifacts.

The animation configuration options—easing, duration, and delay—are documented, but the behavior with rapid successive updates lacks clarity in the official documentation. Additionally, Chart.js maintains internal animation state objects that may accumulate memory during high-frequency update scenarios, though this has not been formally benchmarked in official documentation.

Key constraints include potential differences between Chart.js 3.x and 4.x versions, the need for explicit chart.update() calls to reset interpolation, and possible memory accumulation during continuous updates. No formal benchmarks exist for memory behavior during 1000+ consecutive update calls with animation enabled.

Specific Questions

• Does Chart.js 4.x automatically reset animation interpolation when new datasets replace existing ones without an explicit chart.update() call?
• How does memory accumulation behave during high-frequency updates, and what are the documented limits for animation state objects?
• What is the precise difference in animation state management between Chart.js 3.9.1 and 4.4.0 when using duration: 0 with rapid dataset replacements?