(Server) UntrackedMemory goes up, and never comes down again

[Velibor]

Hi there,

The last few days I’m debugging my servers like crazy, because when they become older they receive a lot of latency.

I rewrote part of the networks twice, but it seems like the server is become clogged with jobs / etc…

What happens

• When the server becomes older, the UntrackedMemory goes up, it also never comes down again… For some reason the server is busy with something, what I really don’t understand since it isn’t listed.

Where does it happen ?
https://www.roblox.com/games/206640076/Roblox-Deathrun
(Reverted the place to a ‘version’ that is kinda OK… If you want a place file that has it way faster, let me know and I will give PM you the latest build that is currently on our Test Servers…)

What have I tried myself ?

• Checked the code a few times, since it seems to happen when large instances are being destroyed (for example a map in a round). I use :destroy() on everything, so it should be GC, or it could be when players leave / enter the game (we do nothing weird with them, just your standard R6)
• Check an other place slot
• Check the Microprofiler for any helpful tips / pointers. (But this is only for the Client correct ?)

Repro
Sadly no repro at the moment

Any more information?
There seem to be users that have the same issue regarding UntrackedMemory.

As objects are deleted in my game, UntrackedMemory goes up, and it never seems to go back down

There is an action in my game that results in the deletion of MeshPart instances and some ValueBase objects. Naturally, one would seem to think that removing these objects would reduce the memory load on the game. But it is creating the opposite effect: as I delete the objects (using Destroy()) the memory goes up, permanently? Obviously this is frightening to me, because if the memory is going up and never going back down, that’s going to crash servers eventually. Is UntrackedMemory something I…

[Chrythm]

This bug has been causing server crashes in a game I’m developing, along with a growing list of other games. I have created a simple repro place file here that allows you to see it for yourself.
untrackedMemoryIssue.rbxl (22.4 KB)

1. Open this place and run a server
2. Start spawning instances until it reaches ~1000 instances
3. Stop the spawner and hit the “Clear” button to destroy them all
4. Watch as the UntrackedMemory jumps up beside the overall server memory

The server memory will never recover from the destroyed instances, even though they are not referenced anywhere.

(Below is an image of the memory after hitting the clear button)

[DivineTempest (Tempest)]

Did you ever get to fixing this problem? I’m having the same issue, have any tips?

[NotRapidV (Rapid)]

UntrackedMemory spikes when destroying models, doesn't go back down

Came across today when I was trying to find some memory leaks in my game. In the video below, you can see I have many cars lined up. Please note that these are only car models, and there are no scripts in them. There are 0 scripts in the workspace; just the models are in the workspace. Then, you can see I clone the car folder two times. Lastly, I destroy all the folders containing the cars. The UntrackedMemory value spikes after deletion of these folders, and never goes back down. I’ve been on …

Having the same issue years later.