Same issue here. After play testing, pressing stop instantly crashes the studio making me reopen it. Very annoying. Happens to all experiences, tested multiple
Looks like im not getting this error anymore? Same with you guys?
Edit: The workspace has no parts in it other than 1 R6 humanoid Rig with a shirt and this is the latest version of roblox studio
1 Like
This occurs for me aswell, but I have only seen it happen with team create turned on
Wow you are lucky. Thats crazy
Nvm its back. The error came back nooooooooooooo
Hi all,
We’re for sure working on this as a top priority. We’re going to try a fix in tomorrows (4/16) release in one area we’ve found, with the understanding that its not going to be a comprehensive fix. I’ll post an update once we expect its fully rolled out and we can see what the difference is. We know this will affect the crash but not the hang (studio stays open but is somewhat responsive and parts of the screen aren’t rendering). And thanks again for sending in reports!
8 Likes
so I’ve been having this situation a lot lately, especially today with one project and here’s what I’ve gathered from my experiences. To me, it seems to be occurring more likely if I enter another app whilst play testing. For example, whilst I code and playtest I listen to Spotify, if I’m playtesting and enter Spotify whilst doing so, that’s going off the app and its freezing more when I’m entering another app to when I don’t enter another app. Ill do some more research because I’m confident this isn’t the cause, its just occurring more to me when I enter a new app.
Another thing I’ve seen is when i enter playtest and i close all my plugins that come up on screen when playtesting, if i do that too quickly it seems to be freezing when i end it, but that’s still only sometimes but more likely when i don’t.
Not sure if any of these things are linked, i doubt it, but thought i would just share.
Hi! In my case, it appears to fix when I press the SHIFT + F5 keybind again. It has a little delay, though.
1 Like
This worked for me. But, my game is larger than normal and takes an extreme amount of time to load.
aka, it worked, but did not work at the sime time.
wait is this true? im gonna test that
that is an entirely different issue from the one we’re facing
Summary
A recent issue has started to occur sometimes where Roblox Studio becomes unresponsive and stops doing anything after I end a solo playtest. I have been experiencing this issue repeatedly, causing me to have to exit out and open the application again and sometimes losing my work because I had not saved right before playtesting.
Expected Results
Roblox Studio should return to the normal editing state after a playtest is ended.
^ Screenshot showing how the application looked after I resized the application. This is its unresponsive state, where the application is not hanging as “not responding” but instead does nothing at all.
^ Oddly enough, pressing the X button to close the application still makes the exit confirmation popup appear, but I am unable to press the buttons on it as well. Pressing the X button will not close Roblox Studio and ending task via Task Manager is required to do so.
^ Another weird thing to note is that I was able to actually save my work in this unresponsive state by using the Control + S keybind, and the output also updated to reflect this. I just discovered this.
Final note: after reopening Roblox Studio, it installed an update. I don’t remember if this occurred every time.
1 Like
Hello all, this is a top priority for us and we are actively investigating.
One important piece of information is the following two questions:
- Are you using the new Explorer, or have you opted out?
- What is your
Workspace.SignalBehaviorset to?
4 Likes
I have this issue and yes I use the new explorer. I believe my SignalBehavior hasn’t been changed from the default.
1 Like
I’m not using the new Explorer, and I have Workspace.SignalBehavior set to Default.
And I’m still having this issue.
1 Like
SignaBehavior is set to Default and I am using the new Explorer.
Just experienced this freeze today after ending a playtest and had to shut down Studio through the task manager.
Not using the new explorer and my SignalBehavior is set to Deferred.
- No, I opted out
-
SignalBehavioris set toDeferred
I’ve been getting this issue recently too, I managed to get the log. I’ve sent you it in DMs.
1 Like
I’m having the issue almost non stop.
- I use the old explorer
- SignalBahavior is set to Immediate