| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 02849 | Crash/Freeze | Critical (emulator) | Random | Jan 19, 2009, 17:26 | Sep 21, 2012, 20:04 |
| Tester | Firewave | View Status | Public | Platform | MAME (Self-compiled) |
| Assigned To | Haze | Resolution | Fixed | OS | |
| Status [?] | Resolved | Driver | |||
| Version | 0.129u1 | Fixed in Version | Build | Debug | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 02849: magdrop, magdropp: Access Violation | ||||
| Description |
----------------------------------------------------- Exception at EIP=004DF955 (deco16_tilemap_34_combine_draw+0x01e9): ACCESS VIOLATION While attempting to read memory at 148C4C38 ----------------------------------------------------- EAX=148C4C38 EBX=0000007F ECX=00000005 EDX=00000002 ESI=0000D0DA EDI=0000916D EBP=0022F8E8 ESP=0022F870 Happened during a regtest, but not reproducible. I also ran it on linux and valgrind once again spit out some warning in the video code. |
||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | magdrop, magdropp | ||||
|
Attached Files
|
 valgrind_24212.zip (1,815 bytes) Jan 19, 2009, 17:26 | ||||
 No.03613
Haze Senior Tester
Jan 20, 2009, 00:37
edited on: Jan 20, 2009, 01:30
|
could it be complaining that the memory that gets allocated in deco16_pf1_data = auto_malloc(0x2000); deco16_pf2_data = auto_malloc(0x2000); deco16_pf1_rowscroll = auto_malloc(0x800); deco16_pf2_rowscroll = auto_malloc(0x800); deco16_pf12_control = auto_malloc(0x10); paletteram16 = auto_malloc(0x1000); (simpl156.c) or dirty_palette = auto_malloc(4096); deco16_raster_display_list=auto_malloc(20 * 256); (decoic16.c) isn't being cleared to a known value? because I can't really see anything else not being initialized, the deco16ic code seems to set everything to a known state.. |
|---|---|
|
No.08939
Firewave Senior Tester
Sep 21, 2012, 17:23
|
The crash hasn't happened in quite a while, but I would like somebody to verify that the valgrind warning is gone before this is closed. |
|
No.08940
Haze Senior Tester
Sep 21, 2012, 20:04
|
I fixed something which was quite likely causing it a while back, so I'd say it was safe to close. |