Memory Leak Traced to Uncleared MutationObserver in Dispatch Dashboard Widget

A routine pull request added an auto-resizing MutationObserver to a telemetry table widget, and QA smoke tests showed flat memory graphs. Six hours into a Monday shift, wallboard monitors running the dispatch app began crashing with Chrome's Out of Memory error. Investigation found that stale closures and an un-disconnected observer kept detached DOM nodes and component trees reachable, so they could not be garbage collected across route changes. An early attempt to fix it by nulling variables in the cleanup function failed because the native observer still held references, and the crashes continued. The proper fix involves disconnecting observers and cancelling fetch streams through a unified AbortController teardown path.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in