Studio Stops Responding When Closed (Cmd + Q)

[edvwards (Edward)]

This afternoon studio crashed on me three times on startup. Since then, I’ve been unable to close studio without using Mac’s Activity Monitor and force quitting the process.

When I press Cmd + Q, which I have always used to close studio, the application stops responding and sits on the above screen. The only way to close the application from then on is using “Force Quit” in the Activity Monitor.

System Specs
MacBook Air
M2 Chip
MacOS Sequoia 15.0
16 GB RAM

According to the activity monitor, studio typically runs at around 3.5 GB RAM when I’m in a place. When I close studio using the aforementioned method, this jumps up to about 4-4.25 GB.

Here is the logfile for my most recent studio session:
RobloxStudio_2025-05-03_00_54_00.log (4.4 KB)

All three of the crashes mentioned above have dump files inside the /crashes/completed folder.

Expected behavior

The expected behavior for this closing studio with Cmd + Q is that the application closes (typically after around 1 second).

[bvetterdays (roman)]

Do you have the new Luau type solver enabled by chance? I had this issue previously and this is what caused it for me. Try disabling if so.

[edvwards (Edward)]

Yes, disabling this beta feature seemed to have resolve my issues. Odd it only started after crashing, isn’t it?