.unmount() memory leak

[wagoon]

Version

3.0.4

Reproduction link

http://wagoon.demoeshop.net/test-remove-vue.html

Steps to reproduce

1. click first button to create new Vue app
2. click second button to unmout it (and delete all pointers to that app)
3. call garbage collector in chrome dev tools
4. create memory snapshot (app is still in memory linked from vue_app)

What is expected?

According to doc, .unmount() in VUE3 is replacement for $destroy in vue2 => this method should destroy all app data to avoid memory leaks
Accordigt to 990803, unmounted app is not allegible for new mount(), so there is no need to store anything aboth it in memory (#1287 (comment))

What is actually happening?

App object stays linked from vue_app and cant be collected with garbage collector

---

Only solution i found is removing the target DIV from DOM
I descrobed all steps in detail on stackoverflow post https://stackoverflow.com/questions/65475604/vue-js-3-unmount-and-memory-leak

[LinusBorg]

Good catch, thanks for the report. PR is already up :)

[happydoop]

Same problem.
I need to dynamically create lots of vueApp in my project, and I use js-lru to cache, as they are evicted from the cache, I unmount and delete, but it doesn't help.

[danielgindi]

"According to doc"... The migration guide does not state that unmount() is a replacement, just that $destroy has been removed, and that Vue instances should not be managed manually. Which is weird, because sometimes you need to.

[wagoon]

Hi
in which version it will be this fix distributed?

[LinusBorg]

Upcoming 3.0.6