Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Possible memory leak when v-for in development mode #8507
Steps to reproduce
What is expected?
Same memory usage after garbage collector
What is actually happening?
Despite the "Performance" tab displays the same memory usage, the "Memory" heap snapshot displays a memory increase.
It get worse when:
Please, consider that:
Thanks for the return @posva .
I also created an issue on vue-i18n, since the memory usage gets way too heavy when using it.
I don't know how much these can be related, but these two packages together with some complex or deeper components structure are taking a lot of memory usage even on production mode.
Looking into Google task manager, my app tab increases by ~2.400K each item I scroll down/up (each one is destroyed/created in the processes).
I'm not used to the core code of vue or vue-i18n, but It looks like the installed components structure are getting copied for each nested component in the app, and the GC can't clean that up after destroy that nested components. It can be the way vue-i18n installs itself, I really don't know. The data below is what makes me think about that: