PlayStation (Sony) and mobile players are unable to join public Roblox servers for our experience.
When these users attempt to join a public server, they consistently receive Error 260 — “There was a problem receiving data, please reconnect.”
However, both PlayStation and mobile players can join private servers normally, and Xbox and PC users can join both public and private servers without any issues.
When PlayStation and mobile players join a public server, the game should load normally and function exactly as it does for Xbox and PC users.
All platforms should connect to public servers without experiencing Error 260 or any data-receiving issues.
Players should see the loading screen, connect to the server successfully, and spawn into the game world with full replication and gameplay functionality.
In short, joining a public server should behave identically to joining a private server — fast, stable, and cross-platform compatible.
Hi, we were able to reproduce this issue on PlayStation. It seems that the problem is being caused by the device running out of memory during game join. This manifests as error 260 when we have a bad allocation for a packet. In other cases, we successfully join the game but crash shortly after due to running out of memory.
We’re still figuring out how to handle this scenario more gracefully by returning something more useful than error code 260 and catching/handling memory pressure before the app crashes. Sorry about this, and thanks for bearing with us.
It looks like a huge number of instances, especially MeshParts, are loaded during game join/start, using a lot of memory. I wanted to ask - does this game have streaming enabled? I was thinking about ways of working around this issue while we’re fixing it in the meantime.
Thanks!
edit: My bad, I see you already answered the question about streaming
Hello, we are continuing to investigate this issue. I saw that you originally posted this on November 7, 2025 at 11pm. I have a few questions:
1.) How long before the post did you first start noticing this issue?
2.) Did the issue begin after a recent update to the experience?
1.) How long before the post did you first start noticing this issue?
Started to occur exactly on the day of the update, October 27 but we tried everything before I reached out here in Development Forums
2.) Did the issue begin after a recent update to the experience?
Yes
And to add, this is the first it happened because in the last 3 versions of the game, I have to admit the game is a bit messy when it comes to assets but they aren’t messy to the point we (the builders of the game) spam parts. If it’s really an optimization issue, then we will start reworking
Thanks for the additional information you provided. From the data gathered, I observed the game is unintentionally leaking memory and allocating a huge amount of memory during experience join. It appears to be platform specific (e.g. PlayStation and iOS/Android) because these platforms have the least amount of total memory, but this effects ALL platforms. I was able to find a positive correlation between Session Duration (how long is spent in your experience) and Total Memory which suggests that platforms with more memory don’t see the crash because they can “absorb” the memory leak for longer periods of time.
To test this theory, I sampled resident set size on macos and observed memory usage of Roblox before and after launching your experience. During experience load, there’s a huge uptick in memory used.
For low memory devices, they typically crash or fail to join during this period
Error 260 is indicative of low memory as this means Roblox failed to allocate memory for network packets
After I loaded into your experience, I observed that memory usage gradually ticks up indefinitely.
For low memory devices that make it past join, they crash shortly after here
NOTE: memory usage across platforms for the same experience can be different, so don’t assume the numbers you see in this graph specifically apply to other platforms; rather just focus on the trend that this graph shows.
Steady increase is within experience without ever moving my avatar
You mentioned that this issue happened immediately after a game update which strongly suggests a bug associated with this update. There are tools that can help you audit your memory usage, see: https://create.roblox.com/docs/studio/optimization/memory-usage
I would suggest investigating the following:
What is causing the steady memory leak
Why is so much memory being allocated on experience join and what was the behavior of the experience before the update that triggered this issue
Please take a look at that and let us know if you have any other questions.
