This marks the fifth major bug from Roblox Studio this year alone, and it’s becoming actually unbearable as a solo developer. The inefficiency and constant disruptions are beyond frustrating. All steps necessary have been done.
A private message is associated with this bug report
Are you sure this is not a problem with Codify itself? It might just be an infinite loop within the plugin.
With how utterly atrocious it is to work with Studio and its consistent incompetence, it’s hard to say if it’s even the plugin or studio. Might be worth I reach out to @cxmeels as well to be sure.
If the problem is an infinite loop, then I guess Studio would still have a bug because it’s not timing-out the plugin ¯\_(ツ)_/¯ I think you should always attempt to resolve issues with specific plugins with the plugin developers first, it might take less time than waiting for a response on a bug report.
Yeah to be honest, that’d be the best course of action moving forward now you mentioned, considering there’ve been times I’ve waited entire months—half a year even—for a proper solution or fix from a team. Appreciate the input.
I’ll look into Codify and see if I can figure out what’s going on there.
However, I’d like to add that resizing windows in Studio in general seems to make my frame rate tank to around 10-14fps, even with all betas and plugins disabled. This is on a Surface Pro 9.
Looks like a plugin issue. Save your vitriol until you’ve confirmed what the issue is. Roblox is not responsible for bugs in user plugins. Infinite loops are not trivially detectable, this is the halting problem. I imagine applying an arbitrary timeout to tooling code that regularly run long processes intentionally would break too many use-cases.
Hi, this looks to be a specific issue with the plugin, as others have noted probably some type of infinite loop or other type of blocking behavior that’s not returning control to the system. There’s not a lot we can do here, I suggest reaching out to the plugin author. Happy to take a look if it turns out this is a badly behaving API we can get a repro for - that’s happened before. If you get more information here, please feel free to post to this thread.
Forgot to reply here but this is fixed in the latest version of Codify. It was due to one of its dependencies essentially updating too frequently (infinite loop within a GetPropertyChangedSignal callback).
cc. @butterthebig