Aug 10 2023 build of BII crashes when desktop loads on MacII ROMs

[adespoton]

https://www.emaculation.com/forum/viewtopic.php?t=11997

I've encountered an odd bug with the latest Basilisk II build (August 10 2023):

Attempting to launch with IIci or IIfx ROMs, it gets through the boot process and then crashes with "Caught SIGSEV at address 0x84d7ff5 ... IMKClient Stall detected ... (invocationInterruptXPCReply) block performed very slowly (5.00 secs)." when the desktop is loading.

Reverting to a build before the "drop a disk image into the window" feature was added makes the crash go away. So does using the Quadra 650 ROM.

[adespoton]

I've done some more digging... originally I thought it was the OS version alone that was the issue, as my 7.0.0 through 7.1.2 configs were crashhing. Then I found that Performa OSes (7.0.1P, 7.1P - 7.1P6, 7.1.2P) would work with the Q650 ROM. Now I've done further tests of 7.0.0 with the Q650 ROM, and it works with the older BII version, but as soon as I upgrade to the Aug 10 2023 build, it still fails.

So it's not just the ROM, and it's not just the OS version. I'll do some more digging as I have time to figure out 1) exactly what combination of OS and ROM have the problem, and hopefully 2) exactly what BII code causes the problem. Of course, due to limited time, it'd probably be faster if someone else figures it out first.

[kanjitalk755]

None of the following combinations reproduced the issue.

Host OS: macOS Ventura 13.5.2
Guest OS: newly installed by System 7.0.smi
ROM: MacIIci.rom / MacIIfx.rom / Quadra650.rom

It may be possible to investigate if the conditions for reproduction are known.

[adespoton]

Good to know; I’ll try with the same setup you used and work backwards towards my custom config to identify the core issue.-Em On Sep 20, 2023, at 5:53 AM, kanjitalk755 ***@***.***> wrote: None of the following combinations reproduced the issue. Host OS: macOS Ventura 13.5.2 Guest OS: newly installed by System 7.0.smi ROM: MacIIci.rom / MacIIfx.rom / Quadra650.rom It may be possible to investigate if the conditions for reproduction are known. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[adespoton]

I've done a fresh install with the new build, and everything works from a clean config from the command line. My previous install that works with the previous build throws an error on boot regarding the Software Update extension on the second reboot (first reboot just quits again). So I haven't isolated the issue, but something has changed that can be overcome.

I'm separately having issues due to the way I personally run the build (I have a hand-crafted app where the info.plist calls a shell script in the MacOS folder that in turn launches an embedded copy of BasiliskII) -- running the shell script directly works, but double clicking the outer app fails. Swapping out to an older version of BasiliskII enables it to work by double clicking. I'm getting no errors in terminal or in any of the logs I can find, so tracking this one down's a bit tricky. But it's also likely to be macOS-related as much as it is related to this app build; probably something in Gatekeeper at play, and not something to fix in the BasiliskII source.

I'll leave this issue open to track things in case I isolate the culprit(s), but I don't think anyone else should bother further attempting to replicate my issues at this point.