Same. This is a memory leak issue. I’ll make another post talking about it js to maybe let more people know, maybe Roblox will see it, but until they fix it there’s unfortunately nothing we can do about it.
If it were a game related memory leak it would just be cause of the code and would be easily fixable, but since it’s a Roblox problem and not a game problem we js have to wait it out.
The good thing is that it seems the leak happens only when you playtest, so this means that as long as you don’t playtest too often you can get away with coding a lot without having to restart every 5 minutes, that’s what I’ve been doing.
It seems like the leak piles up only when you actually start the playtest. It doesn’t increase over time while you’re just in the studio or in the playtest, but rather spikes up when you start the playtest, so if you decide to playtest you can do it for as long as you want, shouldn’t be an issue there.
1 week ago was the last time i opened studio, it ran at a stable 60 FPS or even more (i’m using the familiar 16 GB ram PC not my own 4Gb ram trash pc by the way)
One update between that time really destroyed the performance… my theory that roblox sometimes vibe codes their updates is really becoming strong these days
hello thanks for the response but funny enough the thing got fixed just 30 minutes after writing that message and now it’s stable 60 FPS but i will reply if it happens again
As far as I know, i’ve never used something like that (because I don’t find it necessary), so no
were you having any of the relevant issues that are related to this topic or were you just posting about poor studio performance? (i.e performance drops because of playtesting, etc)
Yo just wanted to come back and say that the issue seems to have been resolved for me. I’ve been coding & playtesting for about 3 hours now, without restarting studio, and I’ve had no issues so far.
I’m still noticing a decrease in FPS per playtest (I have the FPS limit set to 240 and it dropped on the third/fourth playtest to an avg of 130 FPS. This applies to being outside of playtests too. (the FPS not going back up even outside of playtests) So, I’m gonna say no.
But in my case FPS were consistently bad. Now it’s fixed but if this still continues for you or others, then in theory my case was just a different bug from yours. good luck if this still continues I hope you get it fixed
update: for the most part the studio issues are fixed but the memory leaks are still present. i just dealt with studio crashing my entire pc because godforbid I left it open (minimized and in sleepmode) in the background and it memory leaked hard enough that i had to force restart my pc)
I’m a little confused.. Is this relevant to the newly pushed version v737? That’s what I’m currently on and that’s the version still having memory leak issues from the looks of it.
FPS drops are now back with v737 is what I was trying to mention (no playtesting required)., going as low as 11 FPS and or lower sometimes.
Memory Usage has gone from 16% util to 36% and increasing slowly the longer I have studio open. Just in the time of writing this its gone from 36% util to 40%.
at this point it’d be nice to just be able to rollback studio versions when needed than having to deal with a buggy force update or whatever so it’s not impossible to develop/use studio because of performance issues in a recently rolled out update.
I’m a little confused.. Is this relevant to the newly pushed version v737? That’s what I’m currently on and that’s the version still having memory leak issues from the looks of it.
I’m afraid not. The issue I was looking at was not tied at all to a memory leak, and wasn’t live in 737. Those seem unrelated. There was something that was causing a performance drop after you finished your 4th play solo test. (again, not memory)
