Quasar particles memory leak

[Lekeko]

Description
Spawning a quasar particle emitter either by command or by code (entity client side events or renderers, etc...) causes memory leak

To Reproduce
Steps to reproduce the behavior:

1. Create a simple quasar emitter with a particle, no modules needed
2. Spawn in a world the emitter by any way possible

Expected Behavior
The ram spikes up upon emitter spawn and never backs down when it gets deleted, if spawned more and more, the entire system crashes, most cases forcing a system reboot

Screenshots
RAM usage graph

System Information

• Veil Version: 3.3.3
• Minecraft Version: 1.21.1
• Loader & Loader Version: Fabric 0.116.9+1.21.1
• Operating System: Linux (Tested for windows 11 too, giving the same result)
• CPU: i9 - 9900KF
• GPU: NVIDIA RTX 3060
• RAM: 32 GB DDR4

Additional Context
I checked with the
VeilRenderSystem.renderer().getParticleManager().getParticleCount();
VeilRenderSystem.renderer().getParticleManager().getEmitterCount();

and they indeed go back to 0 after it despawns the emitter, but ram is still spiked up and never goes back down

[Ocelot5836]

Can you provide the pack you used for the particles? I'm unable to replicate on my end.

[Lekeko]

stellaria_particles.zip

[Lekeko]

I have been doing some debugging and I found out that :

1. • On a new fabric project, with nothing in the initialize method, spawning the emitter has a really small impact on RAM, but still after some spamming of the /quasar command, it still goes up, slow, the RAM increases in values of around 10-50 MB
2. • On a normal project where I have entities, a custom dimension and some shaders using Veil, rendering at 32 chunks, the RAM usage scales more, but it's not consistent because sometimes it spikes a lot, sometimes barely, the RAM here increases in values of around 100 - 2000 MB, usually the first emitters occupy bigger parts, the size per emitter slowly decreasing as more emitters are spawned in.

On both, keeping minecraft running, the RAM still doesnt go down