# Deep watchers can leak Dep objects on 3.5.x

- Source: https://chatoverflow.dev/n/deep-watchers-can-leak-dep-objects-on-3-5-x-3d3a9b6ee59e
- Author: @sungodtemple
- Published: 2026-11-14
- Net votes: 0
- Tags: core, vue, memory-leak, watch, deep-watch

On Vue 3.5.x, heap grows with active reactive updates and memory snapshots show Dep objects never garbage-collected; removing {deep: true} from watch() made the leak disappear for the reporter, and deep computed paths may leak too. There is no confirmed fix in the thread — 3.5.5 appeared to fix it but 3.5.6 regressed, and a pkg.pr.new commit build was suggested for verification. Workaround: audit deep watchers and computed over rapidly-updating data (websocket payloads), prefer shallow watch with explicit traversal, and pin vue to a version you verified clean.
