Studio leaks ~1 GB/min of memory while idle when Script Analysis is enabled (grows to 100+ GB, then crashes)

Bug Reports Studio Bugs
,
1

My post is AI-Formatted, but the crashes and Script Analysis toggle fix are real.

On Studio 0.730.0.7300790 (Windows), having Enable Script Analysis turned on causes committed memory to grow linearly at ~1.1 GB/min with Studio completely idle (no scripts open, no input). Growth accelerates to ~2.3 GB/min while script sources are being edited. A fresh session reaches 15 GB working set / ~100 GB committed within the hour, at which point the machine (32 GB RAM) hits 95%+ usage and Studio freezes, then crashes.

Disabling Script Analysis at startup stops the leak completely. Toggling it off mid-session does NOT stop the growth — only restarting with the setting already off helps.

This looks like a regression of the March-2026-fixed report: Massive memory leak in Roblox Studio when enabling Script Analysis (languageServices/async grows indefinitely) (same signature: unbounded growth from language services), and may explain the open reports in Massive memory leaks when using studio for an extended period of time

Reproduction steps:

  1. Open a place whose scripts are dominated by large literal data tables in ModuleScripts connected through require() chains. Mine: ~530 scripts; the hot modules are 1,000–6,400 lines each, mostly table literals (game content definitions), all required by one large service module.
  2. Ensure Enable Script Analysis is ON (default). Open the place and do nothing.
  3. Watch committed memory in Task Manager: linear ~1 GB/min growth begins immediately and never plateaus.
  4. Restart Studio with Enable Script Analysis OFF: memory stays flat (~5 MB drift over 3 minutes) even under heavy scripted editing.

Measurements (PrivateMemorySize64 sampled every 20 s, same place and machine, four controlled runs):

Run Script Analysis Activity Result
A ON Editing script sources 17,988 → 24,855 MB in 3 min (~2.3 GB/min)
B ON Fully idle 7,637 → 11,034 MB in 3 min (~1.1 GB/min, linear)
C Toggled OFF mid-session Idle Growth continued unchanged
D OFF at startup Idle, then editing 2,340 → 2,345 MB in 3 min (flat)

Stats:GetMemoryUsageMbForTag during run A shows the growth is entirely engine-internal: Internal = 15,445 MB, while LuaHeap = 435 MB, Script = 203 MB, Gui = 59 MB, Instances = 34 MB, Sounds = 26 MB, GraphicsTexture = 21 MB. Place content is negligible.

System information: Windows 11 Pro 10.0.22631, 32 GB RAM, Studio 0.730.0.7300790.
Beta features: none relevant enabled; LuauSolverV2 FFlag reads false in-session; reproduced with all third-party plugins disabled, edit mode only.

Expected behavior

Script Analysis memory should plateau after analyzing the place, and toggling it off mid-session should stop the analyzer and release its memory.

A private message is associated with this bug report

3 Likes
2

I just upgraded from 32gb ram to 64gb ram and now roblox studio all the sudden uses 6x the amount of memory per instance open and hides the fact that its using it, any idea how to fix?

2 Likes
3

I’m not sure, my problem was that Studio was slowly leaking more and more memory, eventually leading to a crash, disabling “Enable Script Analysis” in Studio settings fixed the problem for me, but you may have a different one.

1 Like
4

I had that same memory leak issue for a while now, the roblox engine is so bad at managing memory usage

1 Like
5

Hello! Sorry to hear you’re running into this.

Beta features: none relevant enabled; LuauSolverV2 FFlag reads false in-session; reproduced with all third-party plugins disabled, edit mode only.

We’ve moved the New Luau Type Solver from a beta feature to a per-place property. The old solver does use less memory, so it can be a remediation for situations like this: check out this post ([General Release] Luau’s New Type Solver) for details on how to use the old solver.

That being said: sharing your place privately (as you’ve done) is enough for us to investigate, diagnose, and fix the underlying issue here :slight_smile:

1 Like
7

hey, whenever I import big packages like react-lua and StudioComponents in edit mode, studio’s memory increases by ~600MB and studio becomes less responsive overall. deleting the packages does not return the memory to its previous level.

i found that disabling script analysis in studio settings completely prevents the issue.

in script analysis, both of them combined report ~1000 warnings with the new luau type solver, which could be the issue

using the old luau type solver decreases the warnings to ~100, which made memory usage rise slower

my studio version is 0.734.0.7340915 (64bit) on windows 10

these are the packages i was importing
react-lua.rbxm (715.9 KB)
studiocomponents.rbxm (634.8 KB)