RAM Leakage after continuous run

Description

The Lavalink Process Does not appear to clean up garbage it collects after some time after the start, I’m not sure why and it doesn’t appear to be normal.

Version info

Client used: NodeJS Erela.JS v2.3.3

Output of java --version:

openjdk 17 2021-09-14
OpenJDK Runtime Environment (build 17+35-Ubuntu-120.04)
OpenJDK 64-Bit Server VM (build 17+35-Ubuntu-120.04, mixed mode, sharing)

Output of java -jar Lavalink.jar --version:

Version:        3.3.2.5
Build:          1222
Build time:     11.04.2021 08:07:27 UTC
Branch          master
Commit:         7b914f2
Commit time:    09.04.2021 17:14:27 UTC
JVM:            17
Lavaplayer      1.3.76

After a Restart of Lavalink: After ~7 Hours Runtime and 1 Player Playing:

[freyacodes]

Whether there’s a memory leak or just poor configuration on my part and other people’s there is something I’m missing here.

It appears to just be you. This issue appears to have been opened because of a misunderstanding about how the JVM manages memory.

[winnipeg21]

Do you use any other flags?

Nope just the xms and xmx as mentioned. I have tried using java -Xms512M -Xmx512M -XX:+UseG1GC -XX:G1HeapRegionSize=4M -XX:+UnlockExperimentalVMOptions -XX:+ParallelRefProcEnabled -XX:+AlwaysPreTouch -jar Lavalink.jar which performed a bit better.