Studio Using Way More RAM than it Should be (25 gb)

Upon launching the studio file for our game CPU usage jumps to around 95% before dropping down to regular levels, memory usage then jumps to around 95% which is around 25 GB for me before slowly dropping back down over time. Other developers have a similar problem in this studio file, but notably this appears to scale with the memory each person has available on their device.

This started occuring a few weeks ago around the time our experience was unflagged from disabling the new IAS playermodule. I don’t know what is causing this specific issue, but if I were to guess it would be related to the large number of custom high poly meshes and 4k textures we have in this place file. These are all stored away properly, but I’m guessing that Studio is attempting to cache them for quick access, causing this issue (could be totally off here). This issue occurs in our development files and the actual experience file (provided for staff).

This has taken development to a crawl as opening and editing the experience file has been extremely laggy since this issue first started occuring. A number of developers with low device memory cannot even open the place file without their computer crashing.

I can’t find anything that changed about our experience or workspace settings, though I have tried disabling a number of workspace properties to no avail.

A private message is associated with this bug report

5 Likes

Hello! Sorry you’re running into this. Something that would help us debug is sharing the affected place files (which you can do in the private message). We’re also aware that the New Luau Type Solver uses a fair amount of memory. You can check if it is enabled by looking at the workspace property Scripting.UseNewLuauTypeSolver: setting this to Disabled could provide some memory pressure relief.

We use the new Luau type solver, but disabling/reenabling this is something we have already tested. This hasn’t created any difference in memory usage. I’ll add the affected place file Ids to the private message.