[ROBLOXCRITICAL] Using an improperly defined variable crashes studio (autocomplete)

[Darkmist101 (Darkmist)]

If autocomplete is on, typing this and other variants of this code will cause studio to cleanly crash (no prompt). Happens on 2 of my Win10 machines.

---
x = -- Definition not finished
x. -- crashes after typing the "."
---

Edit: Since others can reproduce it and it crashes 100% of the time, I’ve changed it to [ROBLOXCRITICAL].

[EmeraldSlash (Rio)]

Yeah, I can repo

However, if x is a local, it doesn’t crash

[GammaShock]

Woah, that’s so weird. This definitely needs to be fixed, people could lose a lot of work otherwise.

[Kiansjet]

Don’t places autosave before running? The only instance in which this would be fatal is if a plugin containing such code was reloaded (possibly via update) during an edit session.

[4wku]

Agreed, Roblox Studio has a default 5 minute Auto Save time I believe… so barely any work will be lost along with the Script Recovery function accessable in Studio that allows you to recover the lost scripts.

[systemise]

@Kiansjet

Don’t places autosave before running?

The crash occurs while in the script editor, not during simulation

Here’s a gif of the issue:

[Luaction]

I can reproduce this on Win7, this should be [ROBLOX CRITICAL]

[Autterfly]

This is actually rather amusing; I was recently working on a lexer style program for Lua and came across an issue when parsing incomplete global statements.

Wonder if it’s the same issue here.

[sleitnick]

Maybe it’s actually a feature to combat bad coding

[Kiansjet]

Repro’d on Win10Pro, agreed that this should be [ROBLOX CRITICAL]

[Silent137]

We’ll have a fix for this in the next release. Thanks for the report!