I recently noticed that if you write any script, in legacy context, that effectively self-destructs at the end when calling “Script:Destroy()” in an effort to save system resources, it will cause the entire engine to appear to freeze frame twice in a temporary but consistent succession whenever called for a split second in the Studio program. I used varying scripts from more complex ones to scripts as simple as merely printing a line of text before self-destructing. I have also employed the script in multiple Roblox places, to ensure that it wasn’t a specific place causing the issue. I am not sure if this issue is also in the “vanilla” Roblox client application. I only tested this in Roblox Studio.
Script self-destruction shouldn’t impact the frame rendering and/or freeze up the entire engine in most cases, unless there were external dependencies causing hangups with other scripts that still exist, etc.
I recreated the script from your video and ran it with an empty baseplate in studio. Unfortunately I can’t reproduce the same stutter that you saw.
Would you be able to retry your test place on your system with the latest release of Studio? I am wondering if the issue has been resolved since you posted the bug.
If you still see the issue, could you send me your .rblx file? That would help me verify that I am testing the exact same experience as you are.
Also, are there any settings or configurations that could explain why I am unable to repro the issue? Perhaps you have some beta features enabled, or studio plugins installed which could be different than my setup.