- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09428 | Crash/Freeze | Major | Have not tried | Apr 3, 2026, 10:55 | 7 hours ago |
| Tester | Robbbert | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Resolution | Open | OS | Windows (x64) | |
| Status [?] | Confirmed | Driver | |||
| Version | 0.287 | Fixed in Version | Build | x64 | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 09428: indy_4610, indy_4613, indy_5015, indigo2_4415 [irix_6_5_hdd]: crashes when demo asked for | ||||
| Description | After booting, there's a "demos" option (didn't try the others). When clicked on, it soon crashes. | ||||
| Steps To Reproduce |
>mame indy_5015 irix_6_5_hdd Wait a while. Soon you'll get a menu which is attached. The graphics are problematic. Move the mouse into the red area above the "demos" icon and click. If you do it properly the icon turns yellow. Wait a bit longer and it crashes. If nothing happens try clicking again - it's quite temperamental. C:\MAME>mame indy_5015 irix_6_5_hdd ----------------------------------------------------- Exception at EIP=00007ff68e0761d0 (mips3_device::code_compile_block(unsigned char, unsigned int)+0x0700): ACCESS VIOLATION While attempting to read memory at 0000000000000000 ----------------------------------------------------- RAX=000000000000000a RBX=000002d170611490 RCX=000002d17cb02990 RDX=000000008b329fec RSI=000002d17061fe50 RDI=000002d166211a20 RBP=0000000000000000 RSP=000000f120cf98f0 R8=0000000000000004 R9=000000f120cf99e0 R10=000002d175ec4fc0 R11=0000000000000001 R12=000000f120cf9984 R13=00000000736e0000 R14=000000000b329fe8 R15=000000f120cf9984 ----------------------------------------------------- Stack crawl: 000000f120cf9cb0: 00007ff68e0761d0 (mips3_device::code_compile_block(unsigned char, unsigned int)+0x0700) 000000f120cf9d60: 00007ff68e02e0c9 (mips3_device::execute_run()+0x0089) 000000f120cf9de0: 00007ff68c3f1d0c (device_scheduler::timeslice()+0x04ac) 000000f120cf9f60: 00007ff68c3ee035 (running_machine::run(bool)+0x0195) 000000f120cff380: 00007ff68f8927eb (mame_machine_manager::execute()+0x022b) 000000f120cff740: 00007ff6938564b5 (cli_frontend::start_execution(mame_machine_manager*, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&)+0x0275) 000000f120cffa50: 00007ff693856c2a (cli_frontend::execute(std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x007a) 000000f120cffab0: 00007ff68f88d247 (emulator_info::start_frontend(emu_options&, osd_interface&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&)+0x0027) 000000f120cffe70: 00007ff6956706b2 (luaopen_lfs+0xcf8442) 000000f120cffec0: 00007ff6886612ee (__tmainCRTStartup+0x016e) 000000f120cffef0: 00007ff688661406 (mainCRTStartup+0x0016) 000000f120cfff20: 00007ffaa4937374 (BaseThreadInitThunk+0x0014) 000000f120cfffa0: 00007ffaa553cc91 (RtlUserThreadStart+0x0021) |
||||
| Additional Information | Tried a couple of other hard drive images, but although there was no crash they were not exactly usable. | ||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | indy_4610, indy_4613, indy_5015, indigo2_4415 [irix_6_5_hdd] | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
1
|
No.24406
Robbbert Moderator
7 hours ago
|
These systems have further regressed; Firstly, although they were able to boot some of the irix images, they would panic when next restarted. This couldn't be fixed until the nvram folder was cleared. Now, in current git they now only show a black screen and nothing works. It's possible to get a red mouse pointer, but that's all. I forgot to point out when this was originally logged that indy_4610, indy_4613, indy_5015 are marked as working. |
|---|