That won’t work for very long, and I’d be careful doing so.
Hi all - we’ve updated a flag yesterday that has addressed 75% of the crashes (studio locks and closes). I’m mentioning this here because its possible there’s a link between the two - if you were crashing the odds are it has gotten better/less frequent. If the freezing has also improved, I’d like to know that. We continue to investigate, thanks for your patience here.
8 Likes
I did think that it was getting less frequent… I just thought i did something to my game.
same frequency (to be exact 100 playtests out of 100 get studio frozen)
upd. pausing physics before stopping playtest fixes the problem, might not be the case but i no longer get freezes
2 Likes
The issue got fixed I think, it doesn’t happen anymore
Personally, it started happening to me about a week ago and is still happening. With the same frequency if you test the game for a long time. Almost all Studio beta-features are disabled. Workspace.SignalBehavior is Deferred.
Please fix it soon, people can’t work normally…
Good suggestion, I’ll try it, hope it helps. Thanks.
For me its started happening yesterday after studio icon change update (flag update). Before flag update all was fine
Its possible this is a workaround as we’ve been looking at some physics updates as a potential root cause. I wonder if anyone else seeing this very frequently can confirm if this stops the freeze for them also. We can repro this on our end, just not very frequently as its very timing/environment dependent as to who gets it.
3 Likes
Hi all, if you’re seeing this a lot and working in Studio this afternoon (next 5-6 hours) we want to try some experiments in tracking down some fixes which would mean putting you on a special install for a little bit.
We’ve also seen that this can be very place dependent, so if you are seeing it in a specific place a lot it would be helpful for us to get a copy of a place if you’re willing to share the place file. If you can help in either area, please DM me with your username ASAP. Also specify if you’re seeing on Mac or Windows. (We’ve repro’d on both but Windows seems a little more frequent)
Having the same issue. Don’t know if anyone has mentioned it, but Autosaves still work while in this state. The normal Studio boots up when opening the file, but it still contains the issue.
Edit for clarification: Autosaves can GENERATE within this state. Again, they still contain the issue, but besides that, it will save like normal.
Hey all -
We have identified a potential fix and just rolled it out. If anyone continues to encounter the hang after restarting Studio, please tag me and let me know. We’re somewhat confident about this fix but are having difficulty finding a consistent repro internally (It’s hard to prove a negative).
4 Likes
After the update you made, crashes, freezes, and similar issues seem to have been resolved, as I haven’t experienced any so far. Now, I can continue editing my game comfortably. Thank you very much!
4 Likes
that’s awesome to hear! I’m sorry that this happened but I’m glad we seem to have found the issue 
1 Like
Howdy,
I’ve done some research for my game, an interesting note,
Upon playtesting my game, Society | Dev Access, on ANY Version old (7 January) and current (14 April), my Memory (RAM) raises to 30k MBs or 30GB+, stops climbing for a short period of time, studio begins “working/playing” and then freezes and continues to climb past 30k or 30GB.
Obviously, I do not allow it to as I don’t want to crash; however, I have 80GB of RAM.
I will post a full video on YouTube and link it for more information.
Still experiencing this as of this post. Just gave up on studio for the day. Hopeful for a resolute fix soon.
Can you confirm you’re getting the play solo freeze after restarting Studio (and ensuring latest version 669)?
1 Like
Problem seems to be fixed w/ 669 !
I’ve deleted all scripts from inside my game. Issue is persisting.
I’ve disabled all plugins and beta features.
I’ve un/re installed studio & roblox > 2 times.
Ram still reaches 31K MBs == 31GB on Client, but reaches 19K MBs == 19GBs on “Run”
- Early reports said to disable beta features from other forum threads, however, the solution did not work.
Studio Vers: 0.669.1.6690663
After chasing down a memory leak of mine, it appears to be an issue with CollisionFidelity “Hull.”
Two MeshParts were causing my game to break, become unplayable in studio, and cause a memoryleak.