EXC_BAD_ACCESS (SIGSEGV) on MacOS 15.1 Developer Beta 2

[xytras78]

BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.

Describe the issue
Attempting to "power on" a VM on the latest MacOS Sequoia 15.1 Developer Beta 2 results in a hard crash of UTM (EXC_BAD_ACCESS (SIGSEGV))

Configuration

• UTM Version: 4.5.3 (99)
• macOS Version: 15.1 Developer Beta 2 (24B5024e)
• Mac Chip (Intel, M1, ...): M2

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.
UTM-2024-08-14-074105.ips.zip

Debug log
For all issues related to running a VM, including crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.

Upload VM
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

[skytoup]

I had this problem too, and after looking at the crash logs, I realized that it doesn't crash as long as the monitor stays on.

[xytras78]

So to add some more color here... after @skytoup suggested it was monitor-specific, I played around and found that the crash only occurs when running UTM on an external monitor. If I run it natively on my MacBook's screen, it works perfectly. But if I move the VM window to an external monitor OR start it on an external monitor, it instantly crashes with the EXC_BAD_ACCESS. I can replicate this 100% of the time. UTM only works with the VM on the built-in monitor.

[kfattic]

UTM-2024-08-22-162308.ips.zip

I'm having this issue, too.