Left Parenthesis Crashing Studio

Hi all,

I’m running into a really weird bug where my Roblox Studio keeps crashing when I type (specifically) the left parenthesis key “(” into a script

I have no idea why this is happening, I haven’t messed with anything recently.

I’ve tried the following so far:

Clearing Roblox Log Cache in Local App Data
Re-installing ROBLOX Studio
Disabling all plugins
Restarting PC

Nothing has helped so far, I was wondering if anyone had ran into this issue before?

1 Like

I now cannot type anything without studio crashing, I had seen the “Restart to update” button on the toolbar less than a minute ago, after updating, all input in my script crashes studio

What on earth…

Is it only affecting the script editor? If you copy and paste, does it still crash?
You already said you reinstalled Roblox Studio. When you did that, did you download a fresh copy from the Roblox website, or did you use an installer you already had installed?

Hey - good questions, so Copy and pasting does indeed work without crashing, seems to only be the script editor I believe, I’ve tried both the command line and just typing into the Explorer and it hasn’t crashed.

In regards to the installation, it was a fresh copy from the Roblox Website (Roblox → Create → Download Studio)

Here’s a video of the situation:

1 Like

Does that only happen in that specific place, or does it happen in every place that you try editing?

If you go to %localappdata%/Roblox/logs and have a look at the recent files there (possibly a crashes folder), do you see anything of note in the logs?

Very weird and possibly critical bug. You should make a Bug Reports. If there is already a bug report, show your experience with it too for a staff memeber to notice it quicker.

That’s a good point, I hadn’t tested that, I just tried it now (see attached screenshot) it doesn’t seem to be crashing!


In regards to the Log files, yeah there’s a few in there, there’s a bunch of txt documents, none in the last 20 minutes, there’s also a crashes folder

Also a good point, I’m still on the fence, especially after I had tested it in a new place, I’m not a regular forum user so I’m unsure of the ‘rules’ but if it’s advised to create a bug report, happy to do so

Have a look if there’s any relevent things in that Crashes folder.
Does scripting work in the problematic place when using a script other than the one that you were using in the demonstration?

(Regarding making a bug report - it’s good to try and narrow down the possible culprit as much as possible prior to making a report, just so they have something to go off. Worst case is they just ask for more information though!)

I’m now realizing just how little I had tested before posting, my bad!

To answer your question, it actually does work! I tested it in a script in ServerScriptService, a module which was a child of that script and a child of the problematic script, no crashes

Which does narrow it down, it seems to be only that script, I’m happy to copy the contents and paste into a new script

Could be worth testing that.

Just tested it and it still crashes unfortunately, which narrows it down more, it’s perhaps the contents of the script?

Possibly. Is there a script that is longer than that one that you could quickly check in, to see if it’s the length of the script rather than the content itself.

(If it turns out to be the content, try copying and pasting the script bit by bit until you get it crashing).

(Make a copy of the original script, in case you do make a bug report)

So my server code is a hundred or so lines longer than this script, seems to be okay, no problems with input or the parenthesis key specifically.

I’ll try my best to strip down the script until I see if I can find what exactly is causing it, I’m gonna start with the Spring Module, since I got on Studio today and that’s the only thing I’ve added

Okay this is me slightly jumping to conclusions but the spring module does seem to be the common denominator, I’ve since tried other methods that include the parenthesis key such as: “script:WaitForChild” or even calling a function from a module like “EffectsService.EjectCasing()”

Haven’t had problems with either, I’ve deleted the spring module from replicated storage and delete any reference to it in the script, input seems to be fine from what I can see now

Other scripts that I had tested didn’t reference the spring module and didn’t have problems with input or the parenthesis key specifically

That is quite odd behaviour. Based on the initial crash when using a parenthesis, I suspect it may have something to do with autocomplete, although I don’t know if that explains why it would crash when typing anything afterwards. The beta feature where they were changing the autocomplete also seems to have ended a while ago, so it’s not something that can be tested easily.

If you’re able to isolate the issue even further (to a particular part of the sprint module), you may wish to make a bug report. Otherwise, you can just carry on with scripting (and hope another issue doesn’t appear…)

I’ve been trying to narrow it down even further and I think you’re right, it seems to be auto complete. Only when the Spring Module is added to my script though. I tried to test other methods of the spring module but after I initially added this line:

local RecoilSpring = Spring.fromFrequency(1,30,5)

If I tried to add any input on the line below for example, studio would crash, as a matter of fact it seems to be any input, anywhere in the script

Therefore I’m unable to test specific methods of the spring module unfortunately, I’ve used this spring module before, haven’t had any problems like this

If you re-import the Spring module into studio (delete it, then reimport), and use the new version instead of the copy that is currently causing the crashes, does it resolve the issue, or does it persist?

Good question - just tried it and unfortunately it persists. Here’s a video (just in case proof was needed)

If you don’t assign the result of fromFrequency to a variable, does the issue still occur (I know this would prevent you from using it, but just for testing purposes)?

(i.e. instead of doing

local RecoilSpring = Spring.fromFrequency(5,30,5)

have just

Sprint.fromFrequency(5,30,5)