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?

[butterthebig]

To confirm, this was on a specific place you opened? Or any place you still saw the issue? As the user above noted, there’s a known issue with the type solver cleaning itself up.

[edvwards (Edward)]

I only tried opening two places at that time. Both had that issue. Both had team create enabled and scripts present (if that helps). I can send you links to the games if needed.

[Yuria_theWitch]

One of the outcomes of some severe (exponential time) performance edge cases in type inference right now in the New Type Solver is that it ends up spinning off in its worker thread in a fashion that is not currently respecting cancellation requests that come from Studio trying to shut down. This is a known issue we’re tracking and working on, but we have a lot of chaos on the ticket side from the different manifestations of this same issue. You can avoid the problem today by opting out of using the New Type Solver while we continue to work on these issues. In the interest of making our tickets manageable, I’m closing this as a duplicate of New Luau Type Solver - Type Solver Doesn't Activate.