When I click play to test the game it freezes and all buttons stop working, nothing is changing on screen. Window functionality remains working (minimize but not close).
A private message is associated with this bug report
Hello! I hope you’re doing well.
Thank you for taking the time to submit this issue and for reading our message.
To help us move forward, we’d appreciate your support with a few questions:
-
Is this issue still occurring on your device?
-
If so, would it be possible for you to share with us a microprofiler dump File, and your system information?
Don’t worry — we’ve got you covered!
You can find step-by-step instructions on how to generate and send the microprofiler [How to post a Bug Report - Bug Reports - Developer Forum | Roblox]. Following these steps will help us better understand the issue and work on a solution more efficiently.
Thank you again for your cooperation!
6 Likes
Hello, I am also experiencing this same problem and the entire studio becomes unresponsive once a solo test is started (play and run). It does not load the physical game or anything it just stops at a blank sky and everything in the studio window becomes unclickable. This happens on both heavy games and blank baseplates. Once this happens task manager is the only way to close studio at that point.
https://devforum.roblox.com/t/studio-solo-test-freezinghanging/4910836?u=decaray
11 Likes
Hello. I am also experiencing a similar issue.
I started experiencing this bug at 2026-10-03T11:00:00Z Before that, the last time I used Studio was four days earlier.
My Studio version is 0.741.19.7411056, and I am using Windows 11.
The symptoms are identical. In my case, the bug occurs in approximately 99% of Play Tests across all Places I have tested. I have tried disabling all plugins, clearing the cache, reinstalling Studio, and restarting my computer, but the issue persists.
All test modes other than Solo Play Test appear to work normally.
Normally, when the bug occurs, Studio freezes with an empty sky displayed in the Viewport. Occasionally, the last scene from the Play Test remains visible in the Viewport, followed by a “Not Responding” state.
I checked the MicroProfiler and observed a significant increase in CPU usage immediately after starting the Play Test, followed by a complete freeze a few seconds later. I tried to inspect the MicroProfiler details, but the CPU load was so high that the text was not displayed properly, making it impossible to examine the details.
Additionally, when the bug occurs, Studio continues to use almost all available CPU resources until it is closed.
My computer specifications are:
CPU: Intel(R) Celeron(R) G5905 3.50GHz
GPU: Intel(R) UHD Graphics 610
RAM: 16GB
I can provide log or dump files if needed.
and English is not my native language, so I apologize if there are any communication difficulties.
(A screenshot taken in the Baseplate)
If the bug keeps occurring and makes testing impossible, try using Server & Clients as an alternative.
13 Likes
Is this bug still being worked on? Server & Clients puts a lot of load on my PC, and it’s getting pretty annoying.
3 Likes
Seems like now it’s just trying to rotate a part. My game plays nice when testing but the moment where I try to rotate a part it decides to freeze the game and for me to close it, I have to use the task manager to do so
1 Like
This is also starting to happen to me, I have to literally close Roblox Studio with Task Manager and then reload it back up again. It’s so annoying 
1 Like
it’s also starting to happen to me right now, but the weird thing is that i have two PCs and only one of them is affected by it for some reason (one is running on windows 10, one is running on windows 11)
also one weird thing that may unblock the situation is that, after i reinstall studio, it doesn’t happen for the first playtest (any games), but the next playtests i launch have that bug
oh also if it can help, these are the specs of the 2 PCs i tested with :
PC 1 : Laptop (not affected)
- 24 GB Ram DDR5
- Ryzen 7 160
- AMD Radeon 680M (iGPU)
PC 2 (affected)
- 16 GB Ram DDR3
- AMD A4-6300
- NVIDIA GTX 750 (dGPU)
even with the crappy specs the PC 2 have, this bug did not happen before like 3-4 days ago
The same bug is still occurring as of 2026-10-10T09:50:00Z
3 Likes