Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Description
Version
2.6.11
Reproduction link
https://github.com/badpunman/vuememoryleak
Steps to reproduce
Clone repository
npm install
npm run serve
open localhost:8080
Open chrome memory tab or other tool for analysis
Click button multiple times.
What is expected?
Vue should release components and the memory.
What is actually happening?
Components are not released.
Continuation to #11755 which was closed with too much haste.
Now demonstrated with $nextTick so we dont have any nasty arguments about whether or not it's due to not cleaning up asynchronous HTTP calls or setTimeouts. $nextTick does not provide a cancellation method so either it's broken in this regard or this is a valid issue.
Vue should not depend its watchers on component if it has already been destroyed.
If this is still not a valid bug, all vue's documentation needs an overhaul as it encourages to write code in a way that allows for memory leaks. $nextTick should then also be removed from codebase.