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

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.

1 Like

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.