Memory leak while simply changing routes

[ricardo-lobo]

Version

2.6.10

Reproduction link

https://codesandbox.io/s/o5znmm1lnq

Steps to reproduce

• Start a new vuejs project with vue-cli
• Add vue-router
• Add an input with v-model
• Type something in the input
• Change route

Chrome dev tools snapshots screens follows:

Base line snapshot

Snapshot while just switching routes

Snapshot after typing in the input

Another snapshot after typing in the input

Another snapshot after typing in the input

We can find all the old "about" components in the memory with the respective data along with it

The memory increase is noticeable when the component is "big"

What is expected?

Its expected to have the vue components correctly garbage collected.

What is actually happening?

Everytime we switch routes after typing something in the input, the vue components count increases by 2 (in the linked example) with the older components remaining in memory with the state attached.

Although this doesn't seem to have a big impact, with complex applications, this can blow up rapidly while increasing memory until the browser tab crashes.

---

In our internal app, every time we switch routes, the memory increase is about 20 megabytes. The components left in memory have big data attached.

[posva]

Closing in favour of #10004 with no router and an html repro