TestFlight: Crash in -[MTLResourceList releaseAllObjectsAndReset]

[osy]

2022-01-14_13-56-33.9214_-0800-07dc5136e6000d702b076c2748efd2e48a2cd5bb.txt
2022-01-14_19-35-02.4437_-0800-0ee2b546a94418dd22874763166517c916b65e0a.txt

[osy]

2022-01-10_14-33-14.0072_+0800-22c67078098676e8da48b2a89f6881cfeeb010a7.txt

[osy]

2022-01-20_01-20-28.8707_+1100-74c03d9c8b89d71fc42b57008314b12df4a57972.crash.txt
2022-01-20_01-23-18.3955_+1100-9e6b8d26729d86e4a89fd6178abb03f08f6ef2f1.crash.txt
2022-01-20_12-14-15.8192_+0100-19e430f2a7fc4e36a38c11f48743ba9f7bc6b707.crash.txt
2022-01-20_12-37-53.7412_+0000-5961616599679092b45444a96fab74e284964757.crash.txt
2022-01-20_21-14-21.9851_-0500-eb7f900f6c22c2ec7c02efaec9a6ea22fd1f940a.crash.txt

[doomguy]

I'm getting this exact crash for weeks now:

Crashed Thread:        12  Dispatch queue: com.Metal.CompletionQueueDispatch

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Codes:       0x0000000000000001, 0x0000000000000020
Exception Note:        EXC_CORPSE_NOTIFY

Any help in sight? Got the paid version from the AppStore..

Edit: I now switched from virtio-ramfb-gl to virtio-ramfb and hope it will solve the issue in the meantime.

[osy]

Yes, GL is still experimental and the crash is due to the GL backend.

[doomguy]

Hi @osy,

to prevent further frustration for others, do you think it might be helpful to communicate experimental/beta features in the GUI, so users can make an informed decision? In this case something like "virtio-ramfb-gl (beta)" or similar would have prevented me from choosing it in the first place. When I setup the machine, I just blindly followed a tutorial online which suggested this setting.

Thanks for considering :)

[osy]

@doomguy So it specifically is listed as "Enable hardware OpenGL acceleration (experimental)" in the wizard and is disabled by default. My understanding of "experimental" is that it could be unstable and I would not use it for a production environment.

[zachyf]

Thank you for marking my comment on #4135 as duplicate. I had another crash that looks similar but might be distinct. Attaching that log. What is the recommended display setting with my configuration other than "virtio-ramfb" that might help avoid this issue?

UTM_crash_log_12-2-2022.txt

[osy]

@zachyf your comment is unrelated. I’ve already moved it to #4745

In the future please do not comment on other issues unless you are certain it’s the same issue. Create a new issue and fill in the template so it’s easier to triage. If it turns out to be a duplicate we will mark it as such.