You should censor the serial/product number for safety concerns.
Thanks! what kind of safety concerns?
You can scam someone out of their warranty if you know their serial number. It’s not exactly something to be parranoid about, but better to keep in mind that it might happen.
I’ve investigated the issue myself a few times and crash logs have lead me to believe this issue is caused by Rosetta 2.
It has never crashed on my MacBook Air (M1) yet. Everything was working perfectly fine on Big Sur stable/beta and now on Monterey beta too.
I also experience crashing on my M1 mac, however it primarily happens when I stop playtesting.
Can also confirm that this still is an issue. This happens around once every day. Last time, I was editing a script, and Roblox just crashed for no reason, and no popups. I am running Studio 0.504, and my Mac is up to date.
Sorry for bumping, but this issue is still happening today. It is quite annoying to loose an entire script because of a crash.
I feel that I am getting something similar on my windows 11 computer.
The original bug report was a crash, but this is a connection error. You should make another bug report.
Ok, thanks, I appreciate your advice.
Yeah the issue is that it closes randomly, no errors from Studio.
I’m running on Apple silicon as well, every time when I press stop from testing or running the game, there is a super high chance that it’ll crash.
This is as Roblox didn’t add native support to ARM macs so it has a chance to crash as Rosetta 2 Isn’t good sometimes. However on my M1 MacBook Pro running the latest version of macOS seems to work fine.
Sorry for bumping but this issue is extremely annoying and has been happening to me for so long.
I don’t know why but it happens randomly and at any given time?
I’m using macOS Big Sur ver 11.2.2 and It just started happening to me, eventually crashes are more & more frequent, this is really annoying can you guys fix this?
You should use macOS Monterey as it’s the latest version of macOS.
macOS Monterey last update 12.5.1 work fast
Did anyone found a solution to this? (I’m using macOS Monterey)
This continues to be a huge issue for development. I believe it is the same error causing this and have sent the logs to the bug reports group