Roblox Studio: Excessive Memory Usage

  1. Launch Roblox Studio
  2. Enter any place file that is saved to Roblox which has a fair amount of content.

Things I’ve tried to resolve the issue:

  • Disabled plugins.
  • Reinstalled both Roblox and Studio. (No system reboot between)

Expected behavior

While I do not have any previous analytics to determine how much memory Studio often would use, play testing results in the program crashing as the memory usage exceeds more than 3/4 of my system’s memory. It seemingly began happening after an update.

This probably happens in other larger places as well, but I’ve only got one for observing this (Exact Place ID and Universe ID included in Staff Notes).

Idle in Studio:
image

Play Testing (Before Crash):
image

A private message is associated with this bug report

1 Like

Hello! What beta features do you have enabled? We’ve seen a good number (though increasingly less) reports of excessive memory usage when the New Luau type solver is enabled. If you have that enabled I would try disabling that.

If that helps, we’d really appreciate a reproduction if you’re comfortable sharing. That will help us root cause and fix this class of issue for other users.

2 Likes

The New Luau type solver is not enabled.

Beta Features currently enabled:

  • Acoustic Simulation
  • Dragger QoL Improvements
  • Improved Find All/Replace All
  • Improved UIStrokes
  • Next Gen Studio Preview
  • Texture Generator
  • UIDragDetectors
  • Video Uploads

Uncertain if this is a issue regarding my system, but if so, I was hoping I could get closure on it not being a Roblox Studio issue, as I’m not sure what to do next.

Salutations!

Thanks for bringing this to our attention.t it.

Could you please provide a log so we can be able to locate the issue?

If you need assistance or info on how to get the logs, please refer to How to post a Bug Report - #12 by Roblox

Thanks for understanding!
Have A Nice Day!

1 Like

0.695.1.6950959_20251017T190410Z_Studio_A40C1_last.log (537.1 KB)
I believe this is the latest log. Hope it helps.

After waiting for about 30 minutes, the Memory Usage returned to something much more manageable. Regardless, it still leaves as to why as of lately, this has become an issue.

Still having issues of needing to wait for a long time. Any suggestions if it’s solely my issue?

Hi, best thing here is to pack up a minimal representation of the place you’re using that is experiencing this, and we can take a look at reproducing on our end. We haven’t seen any systemic rise in memory usage so it might be something localized to what you’re doing.

1 Like

I’ll need to check in with my collaborators to see what new content they may have added. Unfortunately, they don’t seem to be experiencing the same issues, which suggests the problem is likely specific to my system. That doesn’t necessarily rule out Roblox Studio as a factor, but it may be an interaction between the software and my setup. I’m actively trying new things and seeing what I can find. I apologize if this is just an issue on my side of things, I can’t think of any major changes made though to my system that would’ve resulted in this.

I’m closing this one out unless there’s any more information that can help us track it down.

I was unable to find any explanation. The issue still occurs today, but only in that place, and any copies of it. It seems likely that something about the contents of the place is responsible. However, among all of the collaborators, it only affects me, which makes the situation particularly unusual. If there is a larger cause behind this, I hope this post may help others who encounter something similar in the future. If I ever acquire more details, I’ll be back.

You could check the Performance Diagnostics window and look around in PerformanceStats > Memory > CoreMemory/PlaceMemory. That could help.

1 Like

This issue occurs for me too and results in a freeze.
When I go to close it in Task Manager, Studio’s memory usage is around 20,000mb.

What’s most interesting about this issue is that the memory usage will return to something normal after you idle for awhile lol. The drop off is rather instant.

I suppose I could sit here and snapshot the change in these metrics after the memory issue resides. I’ll provide an update shortly.