I’m pretty certain it’s related to this because it’s been happening ever since I’ve seen the new loading UI: Place Open Improvements [Test]
I’m using the term “close” here even though this is a crash to more precisely convey what is happening (e.g. no error messages or anything come up, it just closes)
The frequency is random, but whenever it does happen, it seems to happen back to back for a bit.
Key cases where this has occurred:
Opening place file (.rbxl), and just pressing Play to test will sometimes immediately close Studio
Local Test server and clients will also sometimes all just randomly close
Attempting to sync Rojo will also sometimes close Studio
These occur so frequently I’m often having to reopen Studio multiple times until it finally works.
Hi, we’ll need a bit more info to take action here. In the instances this is happening, is the error occurring during or after the place is fully loaded (i.e. you’ve taken action after the open action, or have been testing the server/clients after they’ve started)?
We’ll also need some logs to help pin down where these issue(s) are occurring. The latest log after an incident would be best - but if you have logs on disk right now mentioning a crash (search for keyword crash, RBXASSERT, etc) we’ll take them right away. You can DM them directly to me.
Studio will open the place file fine, assets load in and you can do things. The second you press “Play” to test, it will show a clear sky and then close after a short bit.
When you open Local Test, it will show the windows for Server, Player 1, Player 2 for a few seconds, and then they close before fully loading.
While syncing in a Rojo project, there is usually a long wait while it does everything. This wait time is expected and usually occurring, however now it will randomly crash Studio during this wait time.
I absolutely believe this is caused by some feature being tested by Roblox. This happens 100% of the time when I see a prompt like this while opening the file (which does not appear every time):
Here is a video of the Play crash shortly after opening the place file, which may help visualize:
I don’t see anything notable in the log file when this occurs, but I’ll send one to you in DMs.
For transparency to anyone else who may be experiencing this, we’ve pinpointed the issue in DMs and a fix is coming (not sure when).
For our problem specifically, it is because we have a very deeply nested tree of instances on a few things and it causes a stack overflow. Hopefully, if anyone else is experiencing this problem, it is the same cause as ours.
For power users who need a fix ASAP, you can try disabling the StudioOpenPlaceOverhaulRollout6 flag in Studio. At your own risk, of course - you never know what might happen by changing these things manually.
I’ll message the logs I’ve generated from repeated window crashes caused by attempting to use the “Local Server” testing option with 1 simulated player tonight - it hasn’t been ideal to not be able to use that workflow when I’ve needed it.
@PolarisWasInDenial I didn’t see anything come through on my end, did you DM me directly?
For reference, the specific issue involved a nested tree ~ 400 levels deep - that should be a pretty rare case, but if you have something like this it is showing up nearly 100% on test runs, and we’re going to have a patch out ASAP. Also DMing as small a reproduction place as possible to me along with logs will help us figure this out faster - once we have a reliable repro on our side these things tend to resolve pretty quickly.
Hi all, I’m closing this one out as the original issue has been patched and verified fixed by @ChasingSpace If you have a reproducible crash, please open another ticket and best thing is to help us reproduce it by describing the pattern in which something happens, providing logs, or a test place if it seems place specific. Thanks!
