09028: imac: Crash at start

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
09028	Crash/Freeze	Critical (emulator)	Sometimes	12 days ago	6 days ago

Tester	Robbbert	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Reopened	OS	Windows 10/11 (64-bit)
Status [?]	Confirmed			Driver	apple/imacg3.cpp
Version	0.272	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	09028: imac: Crash at start
Description	This system will either exit silently at start, or crash with a partial dump.
Steps To Reproduce	>mame imac
Additional Information	C:\MAME>mame -nolog -nomouse imac (SILENT EXIT) C:\MAME>mame -nolog -nomouse imac ----------------------------------------------------- Exception at EIP=00007ff7d1d26884 (handler_entry_write_memory<3, 0>::write(unsigned int, unsigned long long, unsigned long long) const+0x0014): ACCESS VIOLATION While attempting to read memory at 000002b22dcbd440 ----------------------------------------------------- RAX=000002b22dcbd440 RBX=0000000003c00400 RCX=000002b232a80c20 RDX=0000000000380080 RSI=000000006db6db6d RDI=0000000000000000 RBP=000002b222790080 RSP=000000dfbb6f9878 R8=6db6db6d00000000 R9=ffffffff00000000 R10=00007ff7d1d26870 R11=0000000003c00400 R12=0000000003c0000a R13=00007ff7dbbfaea0 R14=0000000000000000 R15=0000000000000004 ----------------------------------------------------- Stack crawl: 000000dfbb6f9870: 00007ff7d1d26884 (handler_entry_write_memory<3, 0>::write(unsigned int, unsigned long long, unsigned long long) const+0x0014) 000000dfbb6f9878: 000002b2228384dd (+0x228384dd) 000000dfbb6f9880: ff00000000000000 (__cxa_throw_bad_array_new_length+0x274d6960)
Github Commit

Flags
Regression Version
Affected Sets / Systems	imac

Attached Files

No.22604 cuavas Administrator 12 days ago	Can’t reproduce. It runs the boot ROM but does nothing useful. No crash or freeze.
No.22618 Fujix Administrator 11 days ago	No repro. Closing quickly.
No.22619 Fujix Administrator 11 days ago	Robbbert, could you stop posting report for systems originally not working?? It pointlessly increases the number of reports and wastes time rechecking them.
No.22621 Robbbert Moderator 11 days ago	Well it crashes for me. I understood that crashing and freezing could be reported even for not-working systems. If that's not the case, and that not-working systems should never be spoken of, then I apologise for the misunderstanding, and I can go through and close all the reports of that nature.
No.22622 hap Developer 11 days ago edited on: 11 days ago	100% repro for me, it crashes 3 seconds after start. 0.272: ----------------------------------------------------- Exception at EIP=00007ff662853081 (handler_entry_write_memory<3, 0>::write(unsigned int, unsigned long long, unsigned long long) const+0x0011): ACCESS VIOLATION While attempting to read memory at 0000026d22815440 ----------------------------------------------------- RAX=0000026d22815440 RBX=0000000003b00400 RCX=0000026d272b5bf0 RDX=0000000000360080 RSI=000000006db6db6d RDI=0000000000000000 RBP=0000026d175a0080 RSP=000000fca13b9988 R8=6db6db6d00000000 R9=ffffffff00000000 R10=0000026d272b5bf0 R11=0000000003b00400 R12=0000000003b0000a R13=000000000000003e R14=0000000000000000 R15=0000000000000005 ----------------------------------------------------- Stack crawl: 000000fca13b9980: 00007ff662853081 (handler_entry_write_memory<3, 0>::write(unsigned int, unsigned long long, unsigned long long) const+0x0011) 000000fca13b99b0: 00007ff65f69b02d (address_space_specific<1, 3, 0, (util::endianness)1>::write_dword(unsigned int, unsigned int)+0x004d) 000000fca13b99b8: 0000026d176484dd (+0x176484dd) 000000fca13b99c0: 0000026d1a898fd0 (+0x1a898fd0) 000000fca13b9a20: 00007ff65e367ba5 (devcb_read<unsigned char, (unsigned char)255>::operator()()+0x0035) 000000fca13b9a28: 000000000000003e (+0x003e) 000000fca13b9a30: f21f494c589c0000 (__cxa_throw_bad_array_new_length+0xef133350)
No.22640 Firewave Senior Tester 10 days ago	Nothing reported with ASAN on Linux. Set is flagged MNW so this report should be invalid.
No.22689 Robbbert Moderator 6 days ago	I found if I comment out either (or both) of the burgundy callbacks, it doesn't crash any more. But it's not easy to discover what the code is supposed to do.