I’ve managed to replicate the bug, so I doubt it’s an issue with your roblox installation.
I’ve managed to discover a workaround - If you go to either the Server window or one of the Client windows (so not the main studio window), the Cleanup buttons in these windows seems to work even when the main one is glitched
Hi there - there’s a couple competing issues here, so I’ll address:
Spamming “stop” when a startup is in progress. The Next Gen Studio playtest controls have a better system for activating/stopping the test, but because of some inherent behaviors in the system we won’t be addressing soon its still possible to prevent the cleanup button from working if you manage to spam it quickly enough - essentially the clients aren’t listening yet to the server, and the signal to close crosses paths with its startup. So there’s going to be an edge case there.
Second is the overall closure behavior. - we have for sure fixed a few issues for a fully started test not shutting down properly. So if you have a repro with the cleanup button for the fully started test we’d love to take a look. Thanks.
I find it very difficult to switch to the improved studio as it makes massive changes to my workflow which has been the same for the past 10 years.
There are also some features still missing in the new improved studio which make it more difficult for me to switch over.
I have tried repeating the steps in the improved studio and it seems this still happens.
If you break the cleanup button using the steps shown above, it permanently breaks the cleanup button in the studio window you make changes to the game to.
I can understand it can break for the specific local test server which is fine but what is frustrating is that it breaks permanently for any newly launched local test server from that point which slows down the workflow over the entire day rather than once a day by mistake.
I just wanted to add - I also get this issue with the same reproduction steps. The local player windows will fail when started because there’s an old server window running that refuses to close when using the cleanup button. I have to manually close every single window when the cleanup button eventually stops working.
So what I’m looking for here are “clean” reproduction steps that don’t involve spamming the button.
Are you saying that 100% of the time the cleanup button never works, even if you allow the serrvers time to start?
The essence of the issue is that currently the system that starts/runs the local server tests is brittle in that there’s a gap when the server starts where cleanup won’t do anything. This gap varies on the machine (case in point - I can’t actually get the behavior you’re describing no matter how fast I spam the button). There’s not currently a good way of fixing this.
We can patch it but its more like “prevent people from shooting themselves in the foot” by putting a cooldown/debounce on the button to prevent spamming. But that feels like a terrible solution as the timing is going to vary wildly depending on the system. On a min spec machine this setup can take literally minutes, and on modern HW it takes seconds. What’s a good cooldown rate there? What number do I put that (a) solves the issue and (b) doesn’t make people wait unnecessarily.
It also doesn’t really solve your problem - but again I want to emphasize the problem statement again:
A) You’re saying that the cleanup button never works
-OR-
B) You’re saying that the workflow when you start a test, but decide against it and want to cancel starting it and quickly hit cleanup doesn’t work.
I think that clarification is important and will help sort this out.
I have noticed the fixes already but couldnt believe it due to it existing for so long haha.
It no longer gets stuck permanently now which is a huge time safer!
Thank you so much for resolving this issue!
I’ve also noticed its easier to stop the launch process of local test servers during the startup process now, have you changed something about that?
It makes launching a new server a lot faster incase i forgot something which helps a lot.
I’m glad to see it’s working for you now! Thank you for providing reliable reproduction steps to make the fix possible.
Improving TTI (Time to Interactive) is a major initiative at Roblox. The fix I implemented mainly addresses the issue when we’re in that bad state (along with some other cleanup-related changes). You might notice additional improvements if you’re experiencing faster responses overall.
