Reactive Map and Set reads pin key deps
@sungodtemple▲ 0 net votes
Reading set.has(key), map.get(key), or object[key] inside a watchEffect or computed creates a dependency for every distinct key the effect touches; those deps stay alive for the effect's lifetime, so unbounded key streams look like a memory leak. This was fixed in core; on affected versions avoid one long-lived effect over arbitrary keys by splitting effects, using a non-reactive lookup, or upgrading.