Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|06933||Crash/Freeze||Critical (emulator)||Always||Apr 7, 2018, 09:05||Jul 19, 2020, 10:07|
|Tester||trebor||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||Resolution||Open||OS||Windows 10 (64-bit)|
|Version||0.196||Fixed in Version||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||06933: adam: During Cassette Activity MAME Crashes With "Caught unhandled St9bad_alloc exception: std::bad_alloc" Message|
|Description||After "Game Over" under Donkey Kong Jr DDP, during soon to follow during cassette activity, MAME crashes with summary error.|
|Steps To Reproduce||
1. Start up MAME with the adam driver loading a ddp image via command line:
mame.exe adam -cass1 "C:\Path\to\Coleco ADAM DDP Images\Donkey Kong Jr (Coleco Adam).ddp"
2. Play a game where cassette loads game fully and the cassette load/play status no longer appears on screen (Typically within a couple of minutes of starting and playing a new game).
3. Allow game to end AKA "GAME OVER" message appears.
4. Now the following takes place automatiocally:
-Tape plays/fast forwards until 25:45.
-Tape rewinds. It hits 00:17.
-Starts to play/ff again until it hits 00:36.
-Rapid rewind. It goes to tape position 00:-4 (?) and crashes.
-Both command line window and the MAME app window close out.
Another user was able to produce a crash with the Zaxxon game as well.
"As soon as I lost all my ships and it flashed the blue screen with different game options, MAME closed itself with message:
Caught unhandled St9bad_alloc exception: std::bad_alloc"
See MAMEWorld posts:
|Affected Sets / Systems||adam|
DKJRDDP.PNG (601,041 bytes) Apr 7, 2018, 09:05 Uploaded by trebor
Capture from recorded video at crash instance.
error.zip (211 bytes) Apr 7, 2018, 11:56 Uploaded by trebor
Error log file produced via Command Line switch.
|There are no relationship linked to this issue.|
Apr 7, 2018, 09:33
In the screen capture the line denotes "mame.exe" as the name as the executable. It is simply the mame64.exe executable renamed, and not the actual x86 executable.
I have hundreds of shortcuts linked to batch files from many years ago that reference "mame.exe". After moving to 64-bit, it was simply easier to copy and rename the x64 executable rather than redo hundreds of shortcuts and batch files.
Apr 7, 2018, 11:54
Launched the game with the Command Line options log & verbose...
mame64.exe adam -verbose -log -cass1 "D:\RNI\Coleco ADAM Images\DDP\Donkey Kong Jr (Coleco Adam).ddp"
Played the game through, same results as mentioned in my previous post. An error.log file was generated. It provides the following information:
[:net4:fdc:u6] ':net4:fdc:u6' (FA7A): unmapped io memory write to 103 = 00 & FF
[:net5:fdc:u6] ':net5:fdc:u6' (FA7A): unmapped io memory write to 103 = 00 & FF
The error.log file upload will follow
Apr 7, 2018, 11:59
Per this post...
...the issue is able to be reproduced...
"...playing dlair and loosing all your lives really quickly."
Jul 19, 2020, 10:07
|Does the exception still happen?|