Can you please DM logs if you’re still seeing this after a full restart of Studio (shutting down all instances). Also include repro rate, etc. We would need to see why yours is different to what everyone else is seeing.
Hi, i have sent a dm and the log since I’m also facing the same problem
The issue no longer appears for me
2 Likes
Hi. Im back, just checking in. I am wondering if this bug is still here. I have been playtesting using roblox client beta and publishing the game. Sadly, this dosent mean any server only run playtesting but it is a quick bandage solution.
In my opinon I have a feeling that only the UI and GUI gets locked or bricked. Which could possibly a problem in a sort of “pipeline” or something connecting the game to the UI.
I had only started to get this issue after roblox devs tried to update the toolbox UI to someting more streamlined and simmilar to the new logo. Its was a bit more responsive.
After the devs had removed it, the bug started to wreck havoc and it had frozen the game all the time.
Thats what leaves to to belive that some dev had forgoten someting while reimplimenting the toolbox UI back and had interupped the “pipeline” which caused an error and had frozen the UI.
Upon looking back at older messages in this topic someone had suggested to disable the new explorer and they said it had worked. Idk man it mihgt just be some bad luck.
Edit: Is this related?
SendLikelySpeakingUsers Event invocation dropped.
If you are wondering whats on server. Radio scilence
No, this seems unrelated.
The consensus on our end is that the issue is fixed as there was a reproducible case on our side that was resolved by changing a flag this past Friday. (With code updates to follow). From above you can see there are still reports happening and we’re working to track these down. The issue being that there can be many reasons for a freeze outside our control, such as errant game code or bugs in 3rd party plugins. We’re looking at some better diagnostics to help resolve this class of problem - we’re far from done here.
The other confusing issue here is that the original problem was not caused by experience code or plugin code but was certainly amplified by the environment - the issue was in physics so certain physics heavy experiences made it happen sooner. It was also highly timing dependent, so your machine + plugins also altered the reproduction rate.
Lastly, there is still a known crash (Studio kills itself, you do not terminate) happening at the same time, which is why I’ve been asking about “crash or freeze” here. That is partially resolved but not fully resolved, but might be soon.