06403: fball: [possible] Fire Ball freezes and resets

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
06403	Crash/Freeze	Critical (emulation)	Random	Oct 9, 2016, 21:08	Oct 14, 2016, 15:04

Tester	D Go Go Fan	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Open	OS	Windows Vista/7/8 (32-bit)
Status [?]	Acknowledged			Driver	capcom/lwings.cpp
Version	0.178	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	06403: fball: [possible] Fire Ball freezes and resets
Description	After playing for over one hour, inserting credits over 12 times, the game Fire Ball will freeze for a couple of seconds, and then the emulated machine will reset. This happened both times I played the game, once after one hour, and once after two hours.
Steps To Reproduce
Additional Information
Github Commit

Flags	Possible
Regression Version
Affected Sets / Systems	fball

Attached Files	fball.zip (4,315 bytes) Oct 12, 2016, 14:29 Uploaded by D Go Go Fan State Save
Attached Files	fballinp.zip (370,831 bytes) Oct 13, 2016, 20:45 Uploaded by D Go Go Fan INP

No.13253 Haze Senior Tester Oct 10, 2016, 11:16	please provide an inp '1-2 hours into gameplay' is too long to really test otherwise. there are 2 copies of the program in the program rom, with a tiny change, maybe one is a bugfix, or it's some subtle protection could just be a buggy game too of course, it's korean.
No.13254 D Go Go Fan Tester Oct 10, 2016, 17:58	I played through the whole game and it did not reset this time. I think it is a bug in the game that causes it to reset sometimes.
No.13255 Haze Senior Tester Oct 10, 2016, 18:05 edited on: Oct 10, 2016, 18:05	would still be good to have an inp for it where it crashes. As I said, the program rom contains 2 copies of the program, with a slight change, would be good to know if that is in any way related to the crash (assuming a replay can play up to the same part with either half) Chances are the hardware only uses one half of it ;-)
No.13258 Tafoid Administrator Oct 11, 2016, 05:29	Acknowledged for now. Hopefully we can get some capture that can be researched.
No.13259 B2K24 Senior Tester Oct 11, 2016, 06:34	I played to stage 5 -1 which took me almost 52 minutes before I had to go and shut it off. I'll do a longer run tomorrow and see if I can repo the behavior.
No.13266 D Go Go Fan Tester Oct 11, 2016, 22:27	I tried to upload a state save I made, but this forum says "file type not allowed". I have a state save made just after the game froze, and before it resets. The screen flips upside down for a split second just before it resets.
No.13268 Tafoid Administrator Oct 12, 2016, 03:40	Try putting it in a .zip container, please.
No.13269 Haze Senior Tester Oct 12, 2016, 18:16 edited on: Oct 12, 2016, 18:18	I don't think such a save state would be useful, by that time it's too late that's why I'm very specifically asking for an inp, not a save state. I need to be able to trace why it crashes, not see that it has crashed and that means running an inp, knowing when it's about to crash / freak out, and creating a cpu tracelog from that point, I can't do those with a save state.
No.13270 D Go Go Fan Tester Oct 13, 2016, 20:50	The issue has something to do with inserting credits / continuing, because every time the game froze was just after I ran out of lives. The INP I uploaded shows the game freezing just after I inserted a credit to continue on stage 3-5.
No.13271 Haze Senior Tester Oct 14, 2016, 15:04	ok, thanks I'm able to play this back, I'll try and do a code trace at some point. I did try it with the other part of the program rom, but the game desyncs early then unfortunately, so I can't tell if that's a bugfix (although logically it seems unlikely that the PCB would be using that part of the rom)