Play testing a game once will result in it working fine- however when you play test the same game for a second time, it results in an immediate crash. I am unsure if this is selective to just myself- however I can confirm it’s not place specific, it happens on all studio instances regardless of the place itself.
No crash dump is created from this- unsure as to why
This seems to only be happening on version-e466aee842f345cf, from what I can tell(?)
Unsure if this is a globalized issue or just myself, if anyone is interested in testing it, that would be helpful for replication.
For whatever ROBLOX Employee that ends up looking at this, if you could send me a private message and I can provide the logs- albeit they are very short, but they do exist
Update:
After looking in to the DMP file alongside the logs, it appears to be an issue with widgets attempting to dock during play testing.
while i cant confirm playtesting crashing me specifically, i do know that it’s to do with widgets recalculating their docks. it happens fairly reliably when you undock/dock certain things (like the animation editor)
This is just one of many crashing instigators that studio has grown recently.
Every single time on the second play test studio crashes completely, luckily I haven’t lost any work through this.
And to reconfirm what @minkmink said, when you go to dock something and you don’t drop a window in a specific region of the docking frames that appear, studio will just crash and unluckily enough, I have lost hours of work through this crash.
I think Roblox should look into following proper logging protocols when studio decides to stop working so we can actually submit proper reports that have a narrow window for debugging.
but you talk all about docking issues, does it fix if you opt into this?
Last time I used this it had a few bugs, hence why I walked away from it.
Nevermind, but okay… I think this has to do with a FFlag, I experienced an issue like this when I was experimenting with Studio. I don’t know which FFlag though.
Thanks, we understand the issue on our end. This was a knock on from another fix we just enabled, we’ve disabled that for now. Glad to hear you are running again.
There was also a redirect to this post stating that the feature with layout adjustments (presumably the one which causes crashes), was disabled for now.
While this crash as a whole is fixed, is it safe to assume that whatever feature was disabled aforementioned in this thread, is still disabled? And the root cause for as to why it was causing crashes is still unknown?