- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
08741 | Crash/Freeze | Critical (emulation) | Always | Aug 4, 2023, 13:13 | Feb 1, 2024, 12:55 |
Tester | 80sRay | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | Resolution | Open | OS | Windows 10/11 (64-bit) | |
Status [?] | Confirmed | Driver | |||
Version | 0.257 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 08741: tmek20: TMEK 2.0 hangs on title screen | ||||
Description |
The T-MEK (2.0, Prototype) set completely hangs MAME a few seconds after reaching the title screen. There's no backtrack since I have to use Task Manager to force quit MAME. The other sets don't crash and seem to work as well as can be expected. |
||||
Steps To Reproduce | Run MAME, choose T-MEK 2.0 and wait. | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | tmek20 | ||||
Attached Files
|
|||||
Relationships
Notes
7
No.21686
80sRay Tester
Aug 4, 2023, 13:15
|
Dupe of 07146. |
---|---|
No.21687
Robbbert Senior Tester
Aug 4, 2023, 14:25
|
Supposedly fixed in MT 07146 (unknown commit), but it's happening again. |
No.21694
Osso Moderator
Aug 12, 2023, 05:42
|
tbh it happens to me even if I launch 0.254, where it was reported fixed. |
No.21930
Kale Developer
Jan 31, 2024, 23:40
edited on: Jan 31, 2024, 23:40 |
Can't reproduce, tried with and without -throttle, Windows 10 over recent-ish 0.261 build. |
No.21931
Robbbert Senior Tester
Feb 1, 2024, 05:42
|
Just tried with 0.262, it ran very slowly (4%) so I quit. This left an error.log of 1.7GB . So I ran it again with -nolog, and this soon became non-responsive exactly as reported. Therefore it's still as much of a problem as it always has been. |
No.21932
Robbbert Senior Tester
Feb 1, 2024, 06:04
|
Summary of error.log - Many lines of 'maincpu' (000A0A): unmapped program memory write to C40040 = 000F000F & FFFF0000 - unmapped memory write to C40000 followed by a read from there. - the remainder of the log is full of bad writes and reads by the 'cage:cpu' which appears to be the main cause of the problem. - eventually the entire thing just freezes, with the error log at 3,272,109,653 bytes. |
No.21934
hap Developer
Feb 1, 2024, 12:55
edited on: Feb 1, 2024, 12:56 |
Yeah, bug still happens to me too. boot game -> title screen -> "insert coin" message flashes a few times -> MAME locks up. |