Investigate potential memory leak

[techniq]

• Open streaming example
• Click Load more on page
• Open DevTools
• Take heap snapshot on Memory tab
• Click Load more on page
• Take heap snapshot on Memory tab
• Click on Snapshot 2 and filter Objects retained by detached DOM nodes
• See also Objects allocated between Snapshot 1 and Snapshot 2

Also, open Performance monitor and click Start on page to stream data and watch the fluctuations on JS heap size (with GC kicking in, but still a general upward trend). More notable, see the large / consistent increase in DOM nodes .

See discussion

---

Investigated streaming performance a few weeks ago when using Canvas and substantially improved the issue, but wasn't able to 100% resolve the issue.

[techniq]

Narrowed it down to something in Axis (Text, etc).

CleanShot.2025-07-02.at.23.59.44.mp4

[techniq]

Reduced by over 90% with a high frequency update over 30s via #586 (released as 2.0.0-next.28).

This also greatly improves the update speed of time axis:

Before

CleanShot.2025-07-03.at.09.16.52.mp4

After

CleanShot.2025-07-03.at.09.17.24.mp4

---

Still trying to track down the remaining leak (it's within Axis) but not making much sense to be at the moment.