Studio crashes when autocompleting "type" with some type-related operations

Bug Reports Studio Bugs
#1

EDIT: Only happens when the AI Powered Code Completion beta feature is enabled

I stumbled on this bug on accident. When you have any sort of script ModuleScript/LocalScript/ServerScript, and paste in this code:

local module = {}



export type t_stats = {
    get: (player: Player | string, statName: string | nil, partition: (string | nil)) -> Instance,
    set: (player: Player | string, statName: string | nil, value: any, partition: (string | nil)) -> nil,
    add: (player: Player | string, statName: string | nil, value: any, partition: (string | nil)) -> nil,
    setFromClient: (player: Player | string, statName: string | nil, value: any, partition: (string | nil)) -> nil,
    getJson: (player: Player | string, statName: string | nil, partition: (string | nil)) -> {any},
    setJson: (player: Player | string, statName: string | nil, value: {any}, partition: (string | nil)) -> nil,
    addJson: (player: Player | string, statName: string | nil, value: {[number | string] : any}, partition: (string | nil)) -> nil,
    removeJson: (player: Player | string, statName: string | nil, keys: {number | string}, partition: (string | nil)) -> nil,
    isLoaded: (player: Player) -> boolean,
    waitForLoad: (player: Player?) -> nil,
}
return module

After you paste in this code and type “type” below “local module = {}” and above “export type t_stats = {” and then pressing the spacebar studio crashes/closes, as shown in this gif:

Gif of me typing “type” and pressing space: https://gyazo.com/28905634d361dfca026699871477ceef

Studio version where this bug occured: Version 0.572.0.5720484 (64bit)

Expected behavior

What should happen is that it should not close/crash studio when trying to type “type”.

A private message is associated with this bug report

#2

Thank you for the report, we have identified the problem and are working on a fix. As a temporary workaround, you can disable the ML Completion beta until the underlying problem is resolved.

2 Likes
#3

Hi Bru,
The issue is resolved. Thanks for bringing this issue to our attention.

2 Likes
#4