| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 07370 | Crash/Freeze | Critical (emulator) | Always | Jul 2, 2019, 09:52 | Jul 2, 2019, 16:49 |
| Tester | MetalGod | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | hap | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) |
| Status [?] | Resolved | Driver | |||
| Version | 0.211 | Fixed in Version | 0.212 | Build | 64-bit |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 07370: sws95, sws96, sws97: Crash during attract mode | ||||
| Description |
Crash during attract mode Regression is mame 0.203 Related to 07369 (regression is the same) |
||||
| Steps To Reproduce | Leave attract mode for a minute aproximately. The game/emulator will crash. | ||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.203 | ||||
| Affected Sets / Systems | sws95, sws96, sws97 | ||||
|
Attached Files
|
 error.txt (5,811 bytes) Jul 2, 2019, 13:58 Uploaded by MetalGod | ||||
 No.16604
Fujix Administrator
Jul 2, 2019, 11:04
|
I left sws95 and sws96 without speed throttling for 5 minutes, there was no crash at all. |
|---|---|
 No.16607
Tafoid Administrator
Jul 2, 2019, 13:11
|
I, too, cannot get either 32 or 64-bit to crash at all using latest version on any machine listed. If it is a release version, it should produce a stack crawl when the emulator exits. Can you post that? Baring that, try installing in a fresh folder and see if that makes any difference. |
 No.16608
MetalGod Senior Tester
Jul 2, 2019, 13:33
|
I've tested several versions of mame, all in clean installations. It happens the same issue from mame 0.203 and onwards. I'm using windows 7 as reported |
|
No.16609
Tafoid Administrator
Jul 2, 2019, 13:37
|
Does it crash at the same place each time? Is there no stack crawl or crash information being printed to command line window? If you try a different video mode,s does it still happen? |
|
No.16611
MetalGod Senior Tester
Jul 2, 2019, 13:43
|
|
|
No.16612
Tafoid Administrator
Jul 2, 2019, 13:49
|
If you run it form a command-window, the stack crawl should be displaying in that window after the screen stays dark. When you close the program after window's dialog comes up, look for the output of the console window. run with "mame sws95 -nothrottle -verbose" |
|
No.16613
MetalGod Senior Tester
Jul 2, 2019, 13:52
edited on: Jul 2, 2019, 13:53
|
Always at the same place. Sometimes there's a Windows error message like the one seen in the video, sometimes don't, it keeps black screen all the time with no error message and with the only solution to close the process. Edited: I'll check that command. Just a second |
|
No.16614
MetalGod Senior Tester
Jul 2, 2019, 13:59
|
Uploaded error.txt |
 No.16615
hap Developer
Jul 2, 2019, 13:59
edited on: Jul 2, 2019, 14:09
|
Here's a crash with sws97:----------------------------------------------------- same crash with -video gdi: ----------------------------------------------------- |
|
No.16616
Tafoid Administrator
Jul 2, 2019, 14:28
|
Even though I still cannot make it crash on my end, hap is a developer who can duplicate the issue and that is good enough for a confirm in my book. |
|
No.16617
hap Developer
Jul 2, 2019, 16:13
edited on: Jul 2, 2019, 16:29
|
It was an array out of bounds access. I don't think it's related to the machbrkr bug. IMO, MAME supporting black_pen() and white_pen() on an indirect 16-bit bitmap is asking for trouble. *edit* correction: I mean 16-bit bitmap, not palette Removing 16-bit bitmaps is on MAME's TODO, problems like these won't happen then. |
|
No.16618
MetalGod Senior Tester
Jul 2, 2019, 16:49
|
That was fast Good work ! ;) |