Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
08580 Crash/Freeze Minor Always 13 days ago 13 days ago
Tester Hirudov View Status Public Platform MAME (Official Binary)
Assigned To cuavas Resolution Fixed OS Windows 10/11 (64-bit)
Status [?] Resolved Driver
Version 0.252 Fixed in Version 0.253 Build 64-bit
Fixed in Git Commit 14afda0 Github Pull Request #
Summary 08580: janyoup2: MAME crashes with Exception
Description When starting to play the game, MAME crashes with following output:

Exception at EIP=00007ff63346a3a0 (register_frame_ctor+0x7b8d20): ACCESS VIOLATION
While attempting to read memory at 0000000000007f1c
RAX=0000000000000000 RBX=000001234968a440 RCX=000001234ae6b5c0 RDX=0000000000007f1c
RSI=000000000000ff1c RDI=00007ff63c731fe0 RBP=00007ff63c6f1de0 RSP=0000001bf3959978
 R8=0000000000000000 R9=0000001bf39598f5 R10=0000003287092778 R11=0000000000000000
R12=f21f494c589c0000 R13=0000000000000018 R14=00007ff63a10d140 R15=0000001bf3959db0
Stack crawl:
  0000001bf3959970: 00007ff63346a3a0 (register_frame_ctor+0x7b8d20)
  0000001bf39599a0: 00007ff62f1d667d (monkeysee_state::~monkeysee_state()+0x000d)
  0000001bf3959a00: 00007ff62f1f8d24 (rtc65271_device::~rtc65271_device()+0x0104)
  0000001bf3959a50: 00007ff62f1da4b4 (nes_jf23_device::~nes_jf23_device()+0x0054)
  0000001bf3959ac0: 00007ff62ed7b7b8 (device_finder<address_map_bank_device, false>::findit(bool)+0x0238)
  0000001bf3959c20: 00007ff62ed78538 (device_finder<a2bus_diskiing13_device, true>::~device_finder()+0x0038)
  0000001bf395f140: 00007ff6323ec6fb (esqmr_state::mr(machine_config&)+0x0035)
  0000001bf395f520: 00007ff634e3660f (register_frame_ctor+0x2184f8f)
  0000001bf395f7e0: 00007ff634e36c1d (register_frame_ctor+0x218559d)
  0000001bf395f840: 00007ff6323e6e29 (construct_ioport_vfx(device_t&, ioport_list&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)+0x0bf4)
  0000001bf395fc00: 00007ff636043a09 (register_frame_ctor+0x3392389)
  0000001bf395fcd0: 00007ff62a2f13b1 (__tmainCRTStartup+0x0231)
  0000001bf395fd00: 00007ff62a2f14e6 (mainCRTStartup+0x0006)
  0000001bf395fd30: 00007ffad1e97614 (BaseThreadInitThunk+0x0014)
  0000001bf395fdb0: 00007ffad2c426a1 (RtlUserThreadStart+0x0021)
Steps To Reproduce Start MAME with the game

> MAME janyoup2

wait for title screen. Press 5 to insert coin then 1 to start the game.
After some seconds of play, MAME crashes with the output in Description.
Additional Information The crash doesn't happen with the parent game Royal Mahjong (Japan, v1.13) (royalmj).

This bug is probably similar to
which was Fixed in Version 0.240
Github Commit
Regression Version 0.227
Affected Sets / Systems janyoup2
Attached Files
There are no relationship linked to this issue.
User avatar
13 days ago
That stack trace is impossible. Your symbols don't match your executable. The stack trace in the issue you linked to is impossible, too. In fact, I'd say the main way the issues are similar is that they both have impossible stack traces.
User avatar
13 days ago
Actual stack trace from a recent build (note that you may have to play for a while before it crashes, it doesn’t crash on starting the game):

#0 0x00007ff73eb6a600 in handler_entry_read_memory_bank<0, 0>::read(unsigned int, unsigned char) const ()
#1 0x00007ff73a2cb03d in z80_device::rm(unsigned short) ()
#2 0x00007ff73a2ee3b4 in z80_device::op_dd() ()
#3 0x00007ff73a2cebe4 in z80_device::execute_run() ()
#4 0x00007ff739e05a23 in device_scheduler::timeslice() ()
#5 0x00007ff739e01d78 in running_machine::run(bool) ()
#6 0x00007ff73d9b9b8b in mame_machine_manager::execute() ()
#7 0x00007ff741076b2f in 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&) ()
#8 0x00007ff74107713d in 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> > > >&) ()
#9 0x00007ff73d9b47a9 in 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> > > >&) ()
#10 0x00007ff7423d8cc9 in main ()
User avatar
13 days ago
I may as well try to untangle some of the mess of dependencies between machine configurations. It’s pretty clear too many things are pulling in the wrong bases.
User avatar
13 days ago
Here is a video of my MAME crashing

I don't know abut the symbols. I am using the official Windows64 version from
I also used the XP 32 bit version (unofficial, unsupported) with same result- crash.

Shall I use a debug version for reporting bugs?
User avatar
13 days ago
Your symbols don’t match your executable if you’re getting completely bogus stack traces like that. A debug build just enables assertions.
User avatar
13 days ago
Did some checking on this.. a 0.226 to 0.227 regression
Specifically, November 2 to November 3, 2020 in my daily build testing. I checked my test notes for that day and this machine was not selected for testing because there were no drivers or devices which affected this. Checking the emulator core files, however, this is the big day of EMUMEM changes:
This is the likely regression point.