Servers shutting down on their own

Recently (within the last week), servers in my game (Theme Park Tycoon 2 - Roblox) started to shut down on their own. This mostly seems to happen to servers that receive a significant amount of load. These servers don’t hard-crash, but seem to soft shut down (invoking BindToClose, for example).

See private content for further diagnosis.

Expected behavior

Servers to not shut down on their own.

A private message is associated with this bug report

13 Likes

Can you give more details about it if possible?

1 Like

I noticed this yesterday in a testing place of mine with just myself and another tester. We were playing the game normally when all of a sudden the soft shutdown script we have set up triggered (which uses BindToClose), teleporting us to a new server. We confirmed the server was not manually shut down or rebooted.

Hope this can be looked into.

2 Likes

You’re not a Roblox engineer so I’m not sure why you’re asking this

3 Likes

Came to further raise notice of this issue as we also are experiencing this in our game (Roblox Party - Roblox). Servers shutdown unexpectedly with error code 288, indicating a “developer shutdown” which is not the case.

Upon further investigation, I suspect that Analytics might have something to do with the problem? Immediately following an unexpected shutdown, this POST request always has a high ping.


Note the 2550ms response time for the client telemetry data

Issue has been ongoing since at least June 7th.

2 Likes

Hello!

Thank you for reaching out about the issue you are seeing.

After internal investigation we have determined that this is a new feature we are experimenting with that is working as intended.

We have made a recent change that will now shutdown the server for an experience if it runs out of memory. Previously when servers ran out of memory they would “hard-crash”.

The memory limits for servers have not changed.

Thanks!

  • PageFaults

We confirmed that the reported behavior is by design. We’re closing this report, but please reach out if you have any additional questions.

4 Likes

Are you sure it’s the same limit? Because this issue started appearing in my game in like the first week of June despite not having made any major changes to it since early May. The peak is 3.83 gigs over the past 30 days.

2 Likes

I have the same concern as the one above but haven’t had a chance to post in this thread. The intended behaviour of this update sounds awesome; keeping players in-game in the event of a crash that would otherwise kick them out, but I feel as if servers are being falsely flagged to be shutdown by this new system. Our game has very low memory usage and there were only 2 players in it at the time. Throughout hours of testing we’ve never experienced a crash apart from this supposed one.

Would appreciate some investigation into this.

Edit: Has been followed up in DMs.

2 Likes

Wanted to follow up aswell… I was in a server today and watched the Server Memory tab the entire time I was playing. The server shutdown at 3.5GB of Server memory instead of the allotted ~6GB. Can other triggers cause this behavior to happen that we should be aware of?

3 Likes

Thank you for the insight.

The memory limits for servers have not changed.

I would love if you guys raised it, it would help a ton for experiences that want to use HQ assets and the newly released high fidelity images

3 Likes

this has been happening in my friend’s game ever since it got decent players

1 Like

any chance you could share anything about what they said in dms? it would be nice if i could get this patched in my friend’s game

I love roblox for this, you just fixed having to deal with data losses and roll backs omggg!!

you think roblox wants to spend more money on servers?

They can reach out to me directly and I may be able to give them some insight for any experiences they own. No guarantees though.

1 Like

This is starting to happen to me when i switched to a server list lobby as my start place. its shutting down the servers once its started and then end up with a teleport failed…