I am not sure why this is happening, but whenever deserializeBufferedPackets is handled on RBX Worker A it seems to be blocking the main thread instead of running in the background. This causes huge frame spikes, some lasting up to 5 seconds
seems to only really happen with games that require constant usage of (Unreliable)RemoteEvents; games that don’t use it (e.g. Survive the Disasters 2) aren’t really affected by this bug use a lot of network?
Experiencing the same issue. Really annoying as I have to reinstall Roblox to fix it but several hours later it reappears and it quite literally freezes my entire client (completely, can’t do anything at all) at some points making me have to use task manager to kill the client.
Thanks for the detailed reports and microprofiler screenshots, and sorry for the inconvenience caused here.
We are actively investigating this issue, and we currently are exploring if this was caused by a regression in some low level replication or task scheduling logic in the latest engine release.
We are working on verifying this theory and pinning down exactly what change caused this, and we will be rolling back the release to address the issue.
The rollback should be completed within the next hour or so, I will update the thread again when that’s been completed.
Telemetry on our end is showing recovery. Do you have a microprofiler dump so we can check that it’s the same issue? Also, can you let me know your Roblox client version? The version is shown in-game at the bottom of the screen when you open Help in the menu, or in the About section of the More page in the app.
Looks like this is a separate issue, would you mind filing another bug report in a new thread with more information such as device, place, logs and a full micro profile dump? Thanks.