Memory leak in 3.11+ (with SSR)

[OndrejSerek]

Environment

**Vuetify Version:>3.11
**Vue Version:3.5.13
OS: Linux

Expected Behavior

The frontend container running SSR should have stable memory usage.

Actual Behavior

The frontend docker container running SSR and Vuetify version >= 3.11 is continuesly increasing memory usage. It takes all the available memory of the server. Then the server crashes.

Our production server was crashing because of this memory leak (the server started crashing when we released update including this Vuetify upgrade) In the picture from Zabbix you can see how stable our server became after downgrading back to the last stable Vuetify version. We repeated this experiment several times in testing environments every time with the same result. The only differences were in Vuetify versions. Version 3.10 is the last stable version without memory leak.

Images

[J-Sek]

If it is hard to pinpoint a specific component, maybe you could bisect until you find the exact version that introduces the problem?

[OndrejSerek]

The first version with this problem is 3.11.0

[J-Sek]

Sorry, I missed that in the description.

[KaelWD]

Can you run the 3.11 docker container locally with node --inspect (exposing port 9229) and hit it with ab or similar until the memory leak starts?

[Nisekoi5]

I'm encountering the same problem. Upgrading vuetify from 3.10.5 to >3.11.0 has resulted in a significant memory leak. Each access causes approximately 10MB of memory usage to increase.
(After downgrading Vuetify to version 3.10.5, memory usage returned to normal.)

During initialization, I clicked garbage collection multiple times and took snapshot 1.
I then used the command ab -s 3 -n 10 http://127.0.0.1:3001/ to access the site 10 times.
After waiting a few seconds, I clicked garbage collection multiple times and took snapshot 2.

I'm at a loss with hundreds of thousands of newly added objects appearing in the snapshots. How can I provide more information?

[KaelWD]

Expand a few ComputedRefImpl in the top panel until you can see fn::(), that should point to the source of the leak.

[Nisekoi5]

Then I clicked on server.mjs:9976 and entered the VOverlay component.