And… back to 277… yarg. Not sure how this happens, but hopefully just gets detected and resolved on the Roblox side.
Can you leave a link to your game?
Not sure if you did something zeuxcg, but I’m guessing you did because I’m not having any further issues. Thanks for checking!
I am getting this error too at random times. In 1 of my games.
This also has been happening to be quite frequently. With my case, there is a slight change, instead of loosing connection, its shows an error with “Account launched from different device” but this could not have happened. I have 2FA to my phone email so no one would have been able to get the code. It’s really strange how this is happening.
Getting this a lot recently, at any game. I am in game for about 1-2 minutes before the “packets in resend queue” starts to go up quickly, then I promptly lose connection.
So this issue has been getting worse for me over the last few weeks, it seems any large game gives me error 277. My internet is fine, computer works for everything else, even larger games than roblox.
P.s sorry for bumping but this issue still needs a fix or a way around it that works for everyone!
Edit: large games can sometimes randomly open…not sure why but it does
This issue started to arise after the beta release of one of my games, Neo-Warfare X.
We had tested this update for close to a year and it worked without issue, but came yesterday and all of a sudden these issues started popping up as reported by my players.
I really do hope this issue can be resolved as soon as it can, as it has affected our player counts especially at this time. I have heard this issue is not just in our games, but in others as well.
I’m experiencing these issues as well with my servers. I have lost a large player count due to this issue. I hope ROBLOX can resolve this issue ASAP.
I have a fast PC and I’m getting this at least 2 times a day.
I also have still been getting Error Code 260 when joining one specific game. I have already tried reinstalling Roblox multiple times just to make sure it was nothing with the software itself. The case is particularily odd as I only get the error code playing one game; I seldom get the error code when playing any other game. I was recently told that the game that I get the error code on has a very high mesh count. Could this contribute to the generation of the error? I also got a new internet router during the time this error code started to propagate. Is it possible Roblox is not recognizing the new router or something specifically on the new game?
In general, I am just perplexed on why I am getting this error and how I can fix it. I would appreciate any support or assistance if you know anything about my problem!
Is this error presenting again for anybody else? My game seems to close frequently due to network errors and I’m not sure if I should go looking around for something I’ve done or wait until a potential fix is out.
Have you tried monitoring the server memory aswell as the clients connection to the server? If I recall correctly the key to bring up the client-server connection starts was Ctrl+F2 or CTRL+Shift+F2, correct me if I’m wrong.
Edit: Its Ctrl + Shift + F3
Sorry for the late reply, I’ve looked through the server code specifically and cleared up any obvious memory leaks, it seems to crash randomly so it can vary from very early on in the server to near the end, it’s unpredictable and untraceable, I’m completely lost on what could be causing it and it’s really hurt any chance of the game being played currently.
The only real things happening on the server frequently is a script firing clients pinging them to get their latency, other than that there’s really nothing complicated at all.
edit:
I should mention that event that is pinging all of the clients happens once every 10 seconds so it >shouldn’t< be too intensive at all.
I know it’s been a long time since I posted this. Though I found the problem back then and I would like to share it as it may help others as well. The issue was that a block I had placed was not anchored and as it was placed on the terrain it was causing the collisions/physics engine to go crazy. That would cause freeze spikes every 5 seconds or so and would end up giving this error. You can check if this is the root of your problem by opening the microprofiler and checking the physics load.
You should get a repro case of that and file it as a new bug report so that staff can fix it properly.
Have to bump this because I myself am suffering from this in my own game. Seems that servers are crashing at completely random intervals, unable to replicate the issue, and nothing was added that seems to have started causing this.
The error code that my players seem to be getting is 277, haven’t seen any other ones. And when reconnecting, it gives them error code 17, which likely means the game isn’t available anymore (server crashed)
If I could get some crash logs from the staff it would be a great help @zeuxcg . Being able to have the logs stored locally upon crashes would be an awesome implementation too, as I have no way of pinpointing the issue.
I’m going to say this, for no reasons at all, a couple of weeks ago Neo Warfare X started having mass server crashes causing 277s for users after the servers VM ran out of memory and crashed, the cause of the issue was a feature that was in the game for over half a year and never showed any issues. Yet suddenly a couple of weeks ago decided to become problematic and begun crashing servers on the regular, dropping the average server lifetime to 1 hour 30 minutes. We’ve checked Roblox Update logs from the time but found no relevant change to Viewports, cloning a lot of parts, or memory management. Yes, the old way we were doing this feature was inefficient but it doesn’t explain why it suddenly started consuming large amounts of memory.
TL;DR Check memory, check Roblox update logs, try looking for what creates a lot of instances, if you have a discord server you can use a webhook to send hourly analytic reports to help track down the cause of the crashes, if none of these work then I recommend taking it up with staff.