UntrackedMemory rises at an alarming rate

[LadyCelastia (LadyCelestia)]

Long story short, I’ve already optimized my server scripts for minimum UntrackedMemory production. But instead, the UntrackedMemory rises at an alarm rate. It can rise up to 100 MB within half an hour with a ~5 player server. Is what I’ve done not enough? If so, is there anymore method to slow down UntrackedMemory gain other than disconnecting events and trashing variables? Edit: Information on my game: 35k parts. A lot of scripts. StreamingEnabled. Voxel Lighting Technology (Not sure if it matters or not).

[goldenstein64 (Shoop)]

I found an interesting article about having to manually disconnect events to players, I’m surprised it hasn’t been patched?

Properly destroy player on leave

The destroy wiki explains that destroy “Sets the Instance.Parent property to nil, locks the Instance.Parent property, disconnects all connections and calls Destroy on all children” As a Roblox developer, it is currently too hard to manually unlink the player signal connections (such as CharacterAdded) to prevent memory leaks and other bugs that may rely on the player connections being disconnected (because you expect certain items to be garbage collected, but they persist indefinitely) If Ro…

I know it’s not much information, but you could try researching the forums for references/instances that aren’t properly deleted, or look at other smaller posts that received solutions to their memory leaks.