00935: New UI problem: Certain Drivers cause the UI to freeze when reloading game.

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
00935	Crash/Freeze	Critical (emulation)	Have not tried	Feb 6, 2008, 17:31	Feb 7, 2008, 15:52

Tester	Iaspis	View Status	Public	Platform
Assigned To		Resolution	Fixed	OS
Status [?]	Resolved			Driver
Version	0.118u4	Fixed in Version	0.122u7	Build
		Fixed in Git Commit		Github Pull Request #

Summary	00935: New UI problem: Certain Drivers cause the UI to freeze when reloading game.
Description	List of drivers that freeze and the list of them who are causing the freeze. 1st run (culprits) atarig1.c atarisy1.c badlands.c cps1.c gaelco.c neogeo.c segac2.c 2nd run (freeze) nemesis.c toaplan1.c toaplan2.c twincobr.c Updated by Iaspis in 0.119: 1) Run edf (megasys1.c) 2) Afterwards run nemesis (nemesis.c). Crashes with: ----------------------------------------------------- Exception at EIP=01216F01: ACCESS VIOLATION While attempting to read memory at 03F7E00E ----------------------------------------------------- EAX=00390006 EBX=03BEE008 ECX=00000048 EDX=00390004 ESI=00FFFFFF EDI=42390006 EBP=0023FD08 ESP=0023FCD0 3) Alternatively run truxton (toaplan1.c). It starts with a terrible speed boost which gets fixed when you start a game. 4) Or run fshark (twincobr.c). Doesn't load (as reported already in newui0118u4ora) 5) toaplan2.c games however seem to be fine ...and the most weird thing is that performing a hard reset after you have run (unsuccesfully) a game of those that have the freeze problem (lets say flying shark) won't do any good. Only if you exit completely mame and restart will it allow the game to run. I always thought that the hard reset function cleans up and recreates everything from the start, as if someone turned the power off and on again. Am I wrong?Furthermore, running an "innocent" random game and going back to the freezer won't do any good either. What a strange bug.. Additional Info from Firewave: Here are some additional information to the edf/nemesis crash: ----------------------------------------------------- Exception at EIP=00F0D96B (m68010_get_info+0x098b): ACCESS VIOLATION While attempting to read memory at 0FB21004 ----------------------------------------------------- EAX=0F791000 EBX=00390004 ECX=00000048 EDX=00000000 ESI=000046FC EDI=00000000 EBP=0022FC38 ESP=0022FC30 ----------------------------------------------------- Stack crawl: exception-> 00F0D96B (m68010_get_info+0x098b) 0022FC3C: 01343DF0 (m68k_execute+0x0370) 0022FC7C: 00CD00BC (cpunum_execute+0x011c) 0022FCCC: 00D1E579 (cpuexec_timeslice+0x01e9) 0022FD6C: 01485470 (ay8910_get_info+0x0410) 0022FFF8: 00401280 (mainCRTStartup+0x0000) Program received signal SIGSEGV, Segmentation fault. 0x00f0d96b in read_immediate_16 (address=3735556) at src/emu/memory.h:1153 1153 INLINE UINT16 cpu_readop16(offs_t A) { if (address_is_unsafe( A)) { memory_set_opbase(A); } return cpu_readop16_unsafe(A); } (gdb) bt #0 0x00f0d96b in read_immediate_16 (address=3735556) at src/emu/memory.h:1153 #1 0x00f0d96b in read_immediate_16 (address=59898) at src/emu/memory.h:1153 Backtrace stopped: frame did not save the PC
Steps To Reproduce
Additional Information
Github Commit

Flags
Regression Version
Affected Sets / Systems	New UI problem

Attached Files