Place in game suddenly insta-crashing - Roblox client PC memory usage rapidly increases to 100%

Help and Feedback Scripting Support
, ,
#1

Not sure if this is an issue with the latest release in the engine so I’m holding off on posting this in bug reports.

I wish there was more info I could provide outside of the title, but, unfortunately I’m essentially gridlocked as even running only a server in studio immediately crashes before eating up all of my system memory. As soon as I press play (or join the place in the normal client), I am entirely frozen. The typical “RobloxPlayerBeta is not responding” when the client crashes is nowhere to be found, and within 5 seconds all 32gb of system memory I have available is being taken by Roblox client - making it essentially impossible to diagnose or troubleshoot.

Our game, Midnight Racing: Tokyo - specifically, our place Tokyo Bay Area has not been updated in over two weeks. Suddenly today, attempting to join the place results in the client immediately crashing (wherein I am unable to access developer console or any other debug tools).

This also occurs in studio for both client play test and “server run” test. I have tried moving basically all of the game’s scripts to ServerStorage to prevent them from running to no avail - although, as stated, the game has not been updated in over two weeks and this is a new issue affecting ALL of our players.

Could this be an engine issue? Potentially content provider related? I know it sounds like a classic case of an unyielding loop, however, as I’ve stated repeatedly the game has not been updated in between this issue not existing and now - and if it is a situation such as this, I have no ability to debug or efficiently search for where the problem is.

Anybody sharing this issue? It should be noted that the place I am mentioning is exceptionally large - with 2500mb+ of memory usage for the map alone being nothing out of the ordinary. Thousands of content provider requests, etc etc.

#2

Have you tried opening an old save of your game? Does the problem still exist in way older versions of your game? Id start there to try and pinpoint where the issue could be, though if that old save works, and no update was made between then anyway, I’d just use that save and not worry about how exactly this even happened anyway.

#3

Great suggestion! However, upon testing this solution, the issue persists. :frowning:

#4

If you use a save during a time you are 100% sure it was working on studio, or even a time slightly before that to give extra room, and it still doesn’t work, I honestly have no idea. Sounds like an engine issue, I’d test in some of your other places to see if it’s a wide rage studio issue, or some freak edge case that you are unlucky enough to have came across. Past that, I’d imagine only Roblox themself could help.

Though, one possibility that I could imagine is maybe some Package changed or something? Since I know those automatically update themself, even in reverts, though I don’t know too much about them, or how that would even cause the issue.

#5

Yeah, unfortunately appears to be an engine thing. I am certain the save that I tested in studio was working for ~2 months before today. While we do use packages, packages still must be published to the game for changes that were made in another place to take effect.

I guess it’s time to move this to engine bug reports, although I still have no clue if it belongs there…