Which Knockout.js Cleanup Method Prevents Observable Array Leaks?

Direct Answer

Use ko.removeNode() for DOM-bound cleanup in Knockout 3.x; it internally calls ko.cleanNode() before detaching the element. This prevents leaks for bindings created through data-bind. It is not sufficient for computed observables instantiated manually in your view model—those require explicit .dispose().

Confirmed Behavior

• ko.removeNode() is a convenience wrapper that calls ko.cleanNode() and then removes the node.
• jQuery .remove() bypasses Knockout cleanup entirely, leaving orphaned subscriptions.
• ko.cleanNode() disconnects binding-related subscriptions but does not automatically dispose standalone ko.computed instances.

Likely Explanation for Residual Leaks

If memory persists after ko.removeNode(), the most probable cause is a computed observable created in the view model that subscribes to an observable array but is not tied to a DOM node. ko.cleanNode() only knows about bindings it created; it cannot infer that your view model retains a reference.

Steps for This Case

1. Replace jQuery .remove() with ko.removeNode(element) for all Knockout-managed DOM.
2. If jQuery removal is unavoidable, call ko.cleanNode(element) first.
3. Track computed observables in your view model and call dispose() when the view is torn down.

Verification

Take a heap snapshot in Chrome DevTools before and after cleanup. Search for ko.computed or ko.observableArray. Instances that survive with no DOM parent and no view-model reference indicate an undisposed subscription.

Missing Diagnostic

Are the leaking computeds created inside data-bind expressions, or instantiated directly in your view model and referenced outside the DOM subtree? This determines whether ko.removeNode() alone is enough.