I’ll be developing in Studio when sometimes I’ll notice that the script editor’s intellisense randomly stops working. Checking task manager reveals Studio is eating up over 20 gigabytes of RAM! Attempting to close Studio while it’s in this state causes it to soft lock and must be force closed through the task manager.
System Info:
Windows 11 Build 10.0.26100
AMD Ryzen 5 5600x
32GB 3200 MT/s RAM
RTX 3060 Ti
Not sure what other info would be of use, so please let me know!
vouch sometimes when i leave studio open while doing something else it increases all the way up to 5 gb (not nearly as much as 20 gb tho, but the normal amount is 2 gb for me) and then studio just wont actually close when i try to make it (this problem has persisted probably since last week or so)
Hey!
Two things:
i know im not the person who created the bug report but i did have the new luau type solver beta feature enabled and now it doesnt stay stuck when i close it (and neither does it memory leak) so thanks for that
The current beta features I have enabled are the following:
I don’t have the new type solver enabled.
I’ll send the place file to the bug files group!
Having this issue in specific studio team creates, in combination with the linked post.
Studio will run at 25GB of Memory, and after 5 minutes will crash the Operating System.
This has been occurring for myself as well, specifically, when I run the game.
Resetting Studio settings returned similar results.
I’ve deleted all scripts from my game, disabled all plugins & beta features.
Running as “Play” for Client, will reach ~31-31.9GB (every time), load the game for a second, freeze, and continue to climb, eventually crashing studio.
Running as “Run” for Server, will reach 19GB, and crash studio.
My game has multiple places underneath of it, and only occurs on the Main starting place. Other places are used for Developer Use only and are private. Our main development area has a larger map/file size the main game.
I deleted every single item in my game. The issue no longer persists.
The issue persists within the Workspace. Specifically inside of these folders. I moved these folders to a baseplate, and the issue occurs.
Discovery!
The issue with these “Computer Screens” was the CollisionFidelity set to “Hull.” The CollisionFidelity set to Hull was causing the part to be “zoomed out” way past map extents and causing a memory leak. AFTER setting the CollisionFidelity to “Box” the zoom focused on the part itself. Running the game presented no issues and was able to play with no increase in Memory.
Problematic MeshPart.rbxm (4.3 KB)
This looks to be a separate issue from the one I’m experiencing, but that’s another crazy memory leak lol
yeah this happes to me all the time when I leave studio for 5 minutes to play a roblox game, then when I come back it suddenly just acts like I spawned in 100k parts, and it’s always fine before I tab into it.
I don’t recall Roblox Studio taking up 7gb of RAM the second I open my place files. Then it just keeps going up to like 10gb after only small changes. I definitely think there’s some serious memory leak going on lately.
Yeah I got kinda similar issue.
It only happens on my bigger game that has a lot of stuff on ( bigger map etc ) - on published version it doesn’t eat the server ram ( Client usage: 1GB, Server: 700MB ) so this is not a memory leak from my side, but in Roblox Studio playtest- it just freezes up and slowly climbs up to 32GB RAM killing my whole PC. Never happened before, just after this recent update
Happening with me too, eating up a gigabyte on the menu while minimized too…
if you need a temporary fix open the studio exe in a hex editor and look for the following bytes
48 81 EC C0 02 00 00 48 8B FA 48 8B E9 4D 85 C0 0F 84 57 01 00 00
replace them with
48 81 EC C0 02 00 00 48 8B FA 48 8B E9 4D 85 C0 E9 58 01 00 00 90
all this does is completely turn off the function where the leak is coming from. If you have any questions feel free to message me.
Thanks! I will try to do that 
In Studio Settings, try disabling:
Autocomplete Suggestions
Type Checking Mode (set it to Off)
Lua Diagnostic Mode (set to Default or Off)
Also, if you’re using a bunch of plugins, try disabling them all temporarily — some of them are memory hogs or don’t play nice with Studio’s internals.
You can also clear out Studio’s cache just in case something got corrupted:
%localappdata%\Roblox\logs
%localappdata%\Roblox\Versions
%localappdata%\Temp\Roblox
(by using Win + R to find the folders)
Another trick: try launching Studio with --fast as a launch flag. It turns off a bunch of the background stuff like script analysis, which makes Studio a bit more stable (but you lose some features).
(Right click Roblox Studio shortcut (desktop or start-up) and click properties, in the target box go to the very end of the line and add --fast, so it looks something like this: “C:\Users\YourUser\AppData\Local\Roblox\Versions\version-xxxxxxxx\RobloxStudioLauncherBeta.exe” --fast, click apply then OK, then launch studio withthag shortcut
Still not a full fix though — I think it’s just something broken with how Studio’s handling the language server or whatever it uses for Intellisense right now. Hopefully they patch it soon.
Thanks for the detailed report! I can reproduce the issue with CollisionFidelity set to “Hull”. Though, this does appear to be a separate issue to the rest of this thread (albeit, with similar symptoms).
Could you paste your response here into a separate bug report thread? It will give the bug more visibility internally, route it to the correct team, and allow us to track resolution independently.
Does this issue occur in playtest only? Or does it also happen while editing.
Only when playtesting. While editing roblox studio uses around 3GB and usage doesn’t rise.
As i said i have quite detailed place, but it worked fine before and in this timeframe i didn’t changed anything in my setup - just installed studio update
