I recently realised that the longer studio runs, the laggier it gets. Ive had studio sessions open for 6-7 hours that are unusable, and resulting in the “not responding” screen
sometimes when i open up a studio place, and run a play test it takes up 1000 mem, in the same place, without changing anything, just using it for longer it starts taking 4000 mem please optimise studio!!
Expected behavior
fix memory leaks on both windows and mac - the mac studio experience is really unoptimised
Thanks for the report! Could you include a microprofiler dump, and your system information?
In-game im getting above 4k mem. But, this happens out of play testing too. Right now my studio is idling at 3.6k Memory, opening up a fresh place is on 1.5k. I also attached an image of the studio browser taking over 3k. This is on my PC, its worse on my M1 macbook. And only for studio sessions that are not fresh, my current session has been open for around 8-9 hours.
microprofile-20250713-152333.html (2.6 MB)
After that playtest specifically, my idle in studio has been increased aswell so i added a dump for that below. I know some concern may be to the placefile i have open, but i assure you thats not the case as i opened the same exact placefile - but in a fresh place, and attached its usage.
microprofile-20250713-152924.html (864.7 KB)
Can you check if “New Laua type solver” Beta is active? If so, does it change the behavior if disabled? (We’ve seen a few of these recently, has to do with particular scripts). Otherwise, is there any pattern for the places you’re working on?
Besides that, increasing in memory during a playtest is pretty normal - that’s going to happen no matter what. And just based on how things work at the allocation level, most of that memory is not being returned to the OS but will get paged out if the system is under pressure. . Once you’ve done a sizable playtest, the system should “stabilize” if you aren’t changing much during edit - the high water mark on memory usage should remain about even. If you’re seeing mem growth on successive runs, that’s for sure a problem.
If its place dependent, we’ll also need a minimal copy of the place that we can reproduce and observe the issue on.
Just encountered this issue without the “New luau type solver” after ending a playtest and waiting about 10mins with my memory going from 8% to almost 90% within seconds and ultimately crashing my entire pc due to running out of memory I can’t seem to reproduce this and it seems to occur randomly
