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.
Sorry, are you still taking about the freeze or memory usage?
1 Like
Both, my studio freezes while the memory climbs after pressing “play” and “run”
My version of the problem seems to be fixed after deleting some “hull” meshes of my own. I will update if the bug returns. For now, try removing them and see if it does anything.
1 Like
Not sure if my issue is related, but I have a problem loading into local player tests. Server sided functions work properly like “Run” (F8) and Start (F7) “Server only”. But with Play (F5), Play Here, Start (F7) client loading seems to freeze then studio exits or crashes. Right before the crash I find the following log in the output / error message.
On Play / Play Here
Failed to connect to 127.0.0.1 | 52418; no response. Connection attempt failed.
On Start (F7)
We could not open the place [0]. Connection attempt failed. Inc. ID: 2261229418642554998
I find that team test in fact works correctly with no issues.
I find this to happen on all games, regardless if new or existing.
I have tried deleting all previous version and fresh install.
I have disabled all plugins.
*See the following reddit post from another user showing the same issue. *
" r/RobloxHelp/comments/1jrmw82/studio_crashes_whenever_i_try_to_playtest/ "
This keeps happening to me as well, really frustrating as this is a sub-place.
Version 0.669.1.6690663
It seems like this problem appeared again, but with a different flavor. Here’s what I’m currently dealing with:
Notice the FPS getting tanked after playtesting, and the docked widgets glitching.
And this is the version that I’m currently using. It recently updated itself to a newer version, which oddly has just spawned this problem. The recent update also changes the splashscreen image when starting Studio.
same here, still happening as frequently and as bad as it originally was.
version: 0.669.1.6690663
doesn’t appear to be the issue on version 0.669.1.6690663 sadly, freezing off playtesting without anything being in the workspace at all
I’m still experiencing the hang, identical to this clip.
- I experience the hang about 5% of the time
- only on complicated places (meshes, scripts, and rojo)
- if i remove any one of the meshes, scripts or rojo sync, I don’t get a hang; only when all three are present do I get the hang
This isn’t the same issue - that was a complete rendering/ui lock. Please file this under a different ticket, so we can route it independently.
This feels like a different flavor - there was a very specific lock causing this issue, not huge memory allocations which could be a bunch of different things. Please file a different ticket for this one, and include as much info as possible on reproduction (best thing is to DM a minimal repro of the problem as an rblx to the ticket private. thread).
Totally unrelated - lets file a different ticket for different problems. Thanks!
Hi, can you describe the problem fully and send a log?