Chart.js and DOM Element Removal: Memory Management during Canvas Detachment

Canvas Lifecycle and Instance Cleanup

When integrating Chart.js (v4.x) into dynamic single-page applications, canvas elements are frequently added to and removed from the DOM based on user navigation. While the .destroy() method is documented as the primary mechanism for cleaning up internal references and event listeners, there is uncertainty regarding the behavior of the JavaScript engine's garbage collector when a canvas element is detached from the DOM without an explicit call to the chart instance's destroy method.

The goal is to determine if the Chart instance is eligible for garbage collection solely through the loss of the DOM reference, or if the internal references maintained by the library create a retainment cycle that persists in the heap.

• Does the Chart.js instance maintain a strong reference to the canvas context that prevents the detached element from being collected?
• Is there a measurable difference in heap allocation between explicit destruction and simple DOM removal?