Almost exactly every second studio freezes for around 50ms which is 6 frames on my 120Hz display, or 3 frames on a 60Hz display. It is consistent and happens without fail. Microprofiler shows ‘Worker’ taking between approximately 48ms and 55ms. I’m not sure when this began, but it’s been at least since the last Roblox Studio update. This post has a suspiciously similar issue but was posted on July 7th.
I have tried disabling all plugins including local ones, testing on a blank baseplate, and restarting my computer. The issue still persists.
Computer Specs:
CPU: AMD Ryzen 9 7950X @4.5GHz
GPU: NVIDIA GeForce RTX 4080 SUPER
RAM: 64GB DDR5-6000
Storage: Samsung NVMe SSD 970 EVO Plus 1TB, Samsung NVMe SSD 980 PRO 2TB
Going to need to bump this thread. This bug still exists in September of 2024.
I’ve tried disabling all plugins, disabling all beta features, and forcibly reinstalling Roblox Studio. None of these methods worked to resolve the issue. This lag issue also exists in all places, both local and published. My computer also has nearly identical system specs to OP’s own setup, with the only significant difference being having 32GB RAM instead of 64GB RAM.
Hoping Roblox notices this issue and returns to work on it. This is intolerable, especially in testing modes. I don’t want to have to publish untested and potentially unstable updates to my game just to test them without lag, nor should I have to do this.
Update: Can confirm that my lag issue is also caused by the “Worker” thread, whatever that is. However, there’s also a lot of presumably graphics-related functions running at the time of the Worker lag spikes. See attached image.
I am also having this issue currently. A few days ago, this didnt happen but now I cant use studio at all because of the Lag Spikes. I also know a few other people who started having this issue the past few days.
I believe we’re still enabling some stuff for this, I don’t think its fully closed on our side from what I understand. That said, there will be other spikes even after this one is closed. For this ticket we’re fixing one specific thing causing these regular patterns.
