Potential memory leak in v-autocomplete component

[v1talii-dev]

First I go to the page https://v15.vuetifyjs.com/en/components/autocompletes then I go to the main page.

I notice separated elements in the developer tools. Can this be considered a memory leak?

in my project I use version 1.5.22, I have the same behavior.

[KaelWD]

Are they still present if you trigger garbage collection?

1.5 is no longer supported anyway, if this is a real bug it would only be fixed in v2

[v1talii-dev]

I tested version 2.6.10 and see detached elements...

[v1talii-dev]

I made memory snapshots using the following algorithm. Went to the page autocompletes. Then to the main page, took a snapshot. And he repeated it three times. In the screenshot, you can see that memory increases between snapshots. Yes, it's probably a project problem with documentation, but it's more likely that it's a problem directly with vuetify.

[KaelWD]

• If you have an adblocker enabled some are retained by the stack traces, clearing the console allows these to be garbage collected
• Some are retained by the search bar not cleaning up after itself properly, fixed by 763af05
• Some are retained by the theme selector not cleaning up after itself properly, fixed by 99e7266
• Some are retained by the click-outside directive keeping a stale vnode reference in scope, fixed by 4d3359a

Heap size seems to be stable around 60MB now instead of climbing into the hundreds after a few navigations.

[v1talii-dev]

Thanks for the quick response and corrections. Tell me, please, is there a problem with detached elements?
P.s.: I did not use an ad blocker in the browser in which the tests were conducted. Of the plug-ins connected, there was only Vue.js devtools

[v1talii-dev]

it can't be related to these problems? vuejs/vue#10085 and vuejs/vue#10004?