Hey guys, I am affected by this bug many times a day. Studio seemed more solid for a while there near the end of last year but now it’s back to where it was. How can I help you track these down?
Describe the bug. Describe what is happening when the bug occurs. Describe what you would normally expect to occur.
I’ll be using the debugger, stepping through some lines of code. I’ll hit Play to resume; studio won’t respond. The blue circle cursor will appear and spin. After waiting (sometimes several minutes) I’ll give up and hit the close button and get the Roblox Studio Is Not Responding dialog from Windows. It’s intermittent enough that the debugger is still a very useful tool, but it is terribly frustrating.
How often does the bug happen (Everytime/sometimes/rarely)? What are the steps that reproduce the bug? Please list them in very high detail. Provide simple example places that exhibit the bug and provide description of what you believe should be the behavior.
Perhaps including you in our Team Build would give you the opportunity to see it yourself. Let me know if you’d like that.
Where does the bug happen (www, gametest, etc) Is it level-specific? Is it game specific? Please post a link to the place that exhibits the issue.
It seems to be specific to the places in our game; they have a lot of code, so maybe it’s an unhealthy interaction in there somewhere. https://www.roblox.com/games/677564321/LegendsI-Common-Models
Like I said, we use Team Build, so maybe that is a factor.
For graphics bugs, it is sometimes helpful to know your system specs, especially graphics card.
This happens on both my desktop and laptop, both running Windows 10, both with 8Gb RAM.
When did the bug start happening? If we can tie it to a specific release that helps us figure out what we broke.
It’s been happening since the early days of our project. I am sorry I didn’t report it earlier.
Anything else that you would want to know about the bug if it were your job to find and fix it.
Let me know how to send you logs or crash reports; I used to know how to do this but I’ve forgotten.
I think it always happens whenever you pause the simulation for more than a few seconds. Whenever the thread then finally yields, allowing other code to run again, it will lock up all of studio. If you let it pause for only a few seconds, then run the simulation again, I always notice a lagspike where it catches up again (well, it feels that way).
Definitely very annoying when pausing at a breakpoint and inspecting symbols…
It feels very similar to back when it also froze studio whenever a script times out due to not yielding for a long time: it would nicely show the popup that the script was running for a long time, but then actually stopping that script locks up studio (i.e. other stuff is trying to catch up?). That issue got fixed for me, though.
We do have dozens of modules. Hopefully that’s a clue. It’s a large project.
Another possible clue: it is almost always slow to come back from the debugger via pressing play; usually in the neighborhood of five seconds or so. Sometimes if I wait long enough it does come back. Sometimes I’ll go make a sandwich and it will still be locked.
Windows 10 (I mentioned that but I can understand missing it in the wall of text)
Yes, the other coders on the project have seen it. I just asked one to check just now and he repro’d it the first try.
While it would be too time consuming to try and make a smaller place that isolates the lock, I could probably figure out a consistent series of steps to reproduce it with our project. Would you make use of that?
This simple script consistently reproduces the issue for me (Win 10):
wait(1)
game["Run Service"].Heartbeat:Connect(function(dt)
local useless_value = dt
end)
local another_useless_value = 1
Hook a breakpoint before local another_useless_value = 1, run the simulation, wait for ~10 seconds after it breaks, then continue the simulation and Studio will freeze up. Removing the connection to Heartbeat will prevent this issue for me.
Not to “necrobump” but this is still a bug or it has be reintroduced I believe. I can’t use the debugger for more than a few seconds without my game “not responding” after stopping the simulation.
I have multiple loops client and server side running constantly as well as a ton of linked modules, shouldn’t make a difference though.