Place Specific Studio Memory Leak

I’m encountering a critical memory leak in Roblox Studio that only affects one specific experience. The issue causes memory usage to balloon rapidly over time, even when the Studio window is idle.

Repro Steps:

  • Open the affected experience in Roblox Studio.
  • Do not press Play, Simulate, or interact with the viewport beyond letting the project sit open.
  • Observe Task Manager

What Happens:

  • Memory usage for Studio rapidly increases.
  • After ~3–4 minutes, memory usage reaches around 20 GB, pushing total system memory usage to 97%.
  • This persists even without any user interaction or simulation running.
  • Eventually, the system becomes unstable due to RAM exhaustion.

Notes:

  • This only occurs for one specific experience. Other places open and remain stable in Studio without issue.

System Info:

  • OS: Windows 11 Home, 10.0.26100 Build 26100
  • RAM: 32GB DDR4
  • Studio Version: 0.679.396.6790000

Expected behavior

  • Memory usage should remain stable when Studio is idle, especially with no simulation or editing activity.

  • I have already tried:

    • Reinstalling Studio.
    • Restarting the computer.
    • Checking for rogue plugins (none are loaded in this case).
  • There are no scripts or assets running in the background—just the open experience file.

The experience in question is:

4 Likes

Do you have any beta features enabled? We’ve seen this behavior with the new type solver beta in the past, so if that’s enabled you may consider disabling it and seeing if that works.

4 Likes

Yep that looks like the culprit.

1 Like

Thank you for beta testing the new solver, and sorry to hear you’re running into an issue. Would you be comfortable sharing the place in question?

2 Likes

Heya, no worries. I forgot that it was even turned on. Do you mean the place file?

1 Like

Yep, the place file as a direct message. As my coworker mentioned, this class of issues is something we are tracking for the new solver: there are improvements in flight, but it’s good to know if we’ve gotten this case or if this is something we’re missing and can do better on.

1 Like

That memory leak persists if the game have large scripts, no matter if you have deleted them, the only solution to remove it is to disable that beta, they remain as if they were ghosts.

  • in a testing place I had a module that worked as a database with 14.000 lines, that system was abolished and replaced by a more optimized and compact one.

  • But when I tried to open it, the map was black, as if it could not load, and even the icons of the Studio interface did not load.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.