(please excuse the lengthy and somewhat misleading title)
I’m not really sure how to describe this bug, since the way to cause it is very unorthodox and specific to my case, despite this I’ll try to explain the issue.
I’ve found that requiring a ModuleScript that contains a breakpoint after it has been set to be destroyed (or its parent set to nil) will cause the debugger to glitch out.
You can replicate this by creating a ModuleScript and adding one breakpoint inside and running this command in the command bar.
local targetModule = workspace.ModuleScript
task.defer(function()
targetModule.Parent = nil
end)
require(targetModule)
I would like to note that the parent of the ModuleScript doesn’t matter as long as it isn’t nil initially.
The only way to exit the debugger at this point is to open (or create) another script and click “Resume Scripts”. (which is fine)
The problem is that trying to exit and save will cause Studio to hardlock, and will require some other application, like task manager, to close it.
Expected behavior
The debugger should not be triggered (or should exit) if the script is parented to nil.