Roblox studio in my specific game place (RoVille đď¸ - Roblox) takes about 6GBs (!) of memory.
Which is slightly alarming in itself, but the main issue is that it climbs even higher to 8gb when playtesting, and it crashes a few seconds into the client loading in. (Note: my system still has several GBs of available RAM when it crashes)
Also note that when playtesting through a local server, neither the server or client crash and is currently the only way I can playtest the game.
Expected behavior
Studio shouldnât crash unexpectedly since there is sufficient available RAM.
Perhaps there is also a memory leak causing this absurd amount of memory?
This game never used to crash when playtesting in the past. This issue started happening these past few weeks
The difference between the play solo and the local server/client is that everything is hosted in a single process. So if the data model for your place is already churning through a lot of memory its going to be done in triplicate in the same process as we clone the server DM and then the client DM is created and replicated into. It certainly feels like this is an out of memory situation given that things still work in the other processes. Thereâs a lot of reasons why you can fail to allocate memory and crash, but the important thing to discover here is why your place is taking so much memory.
A memory leak would imply that the system usage grows over time. Generally this would happen after mulitple play tests, but sounds like this happens on the first try? Does it hit 6GB only after a few play tests, or right away after opening the place? Have you recently incorporated any new features or structural changes in the place? Turned on any beta features? Added new plugins?
Studio hits over 6gb as soon as everything loads in. Then on my first playtest it skyrockets to almost 9gb before crashing. I have all beta features turned on automatically.
However, I disabled all beta features, and it seems to be running perfectly in play solo now. Still taking out around 9gb of memory on playtesting, but at least not crashing. So it seems as if this issue is not a memory issue, but a bug related to a beta feature.
Hard to figure out which one it is, cause theres quite a few to toggle. Will try to pinpoint the actual beta feature causing this once I have more time.
The Crashing is originating from the new studio docking widgets beta. There was another bug report about the crashing and evidence was provided from the crash dump that studio didnât like the new docking behaviour.
I can also replicate the docking crashes by simply just moving a window to another location on my screen, if I donât drop it within 1mm of the target zone studio dies while calculating where itâs going to go.
The issue with playtesting was that when the player loaded in it is trying to calculate where the windows are going to be readjusted to. (Atleast from what I remember).
After turning the docking behavior beta off, it works perfectly.
Sorry, is this account an alt for the OP? Would be really helpful if this behavior is consistently repeatable to get a video of it. Weâve been closing out crashes with the beta so would like to get to them all before we push it to everyone. Iâm not sure how moving windows around would affect going into PlaySolo, but maybe its an issue with the layout in general? We can also have you turn on the beta and reset the layout, but for now a video of the crash if you can repeat it would really help.
