Issue:
I was testing in studio and all of a sudden my game freezes and I check task manager and see that all of my memory is being used up, I also noticed this issue when I was using Roblox Pathfinding Service.
When you block the pathfinding path your memory gets fully used up and studio game freezes.
I have no idea how to re-create this issue besides just playing the game in studio, my code hasn’t done this before and I haven’t changed it.
System Specs:
I5-13600K
32GB 6000HZ DDR5 RAM
4070
Windows 11 Pro
Dump files were attached to the internal ticket by a Roblox Staff (@Focia19) as they may contain sensitive information, will not be made public!
Does that say 22GB? I’ve also had issues with excessive Memory issues with it reaching 2/3GB of ram. I also haven’t had these issues before, I’ve been mainly seeing this issue for the past month or so.
Wow, I’ve never seen a game use that much RAM in Roblox. That’s 100% an issue, the most I’ve seen a game use was about 4GB and the game had a lot of stuff.
Something similar has been happening to me on my Mac. At completely random times, I get an alert that I ran out of application memory, and that Roblox is using ~60GB of application memory, so I’m forced to restart studio. The number usually rises at around 100MB per second until it reaches the ~60GB cap. I don’t have any problems on Windows so far, though.
Using 2+ local player test servers on Studio can rack up a bunch of background processes, even if you use Cleanup. After about an hour of testing, I noticed my PC’s RAM was using 20/32GB with nothing running (not Roblox Studio either). Looked at my background processes and had around 5+ Roblox Studio background processes with atleast 2-3gb in use along with other smaller Studio processes taking up a smaller amount of GB. Solution was to end all those tasks separately.
the only time this memory leak happens is when the path is blocked, when it’s blocked it’s supposed to repath and use the new path but instead studio starts to meltdown
Hello, bumping this thread one last time to see if this is still an issue or if the memory fix has addressed it. Marking the issue fixed for now; we hope that you are back up and running but please let us know if not!