Open ferferga opened 1 year ago
This comes with huge delay, but there have been a lot of advancements in this regard.
Though Vue still has many Suspense issues when combined with transitions, I'm almost sure the exact source of our leak is on Vuetify's side, since the antfu's repo was GC'ed correctly and many other complex demos with Suspense + Transition did too.
While profiling in our client, all the references pointed me to VBtn
, which lead me to focus on Vuetify only. I posted this on Vuetify's Discord the 08/06/2023 (DD/MM/YYYY):
I didn't open an issue in their repo yet since I still didn't have conclusive results.
For future reference, as of v3.4.11 Vuetify has been fixing memory leak issues since v3.4.6.
v3.4.5:
v3.4.6:
v3.4.8:
v3.4.11:
Description of the bug
There's a memory leak with DOM elements not being detached correctly in master when switching between pages, so long-running sessions of the client might make the browser consume a lot of memory.
I believe this is caused by a combination of
Suspense
(which is still beta) andTransition
, as showcased in https://github.com/antfu/repro-vue-suspense-transition-memleakI'm still trying to isolate all the dependencies as much as possible to triage where this is coming from exactly, since this might not be a Vue bug.