01691: Various Sets: when exiting a game, seems to be any game I get an eip error

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
01691	Interface	Major	Always	Apr 9, 2008, 17:33	Apr 17, 2008, 04:51

Tester	user247	View Status	Public	Platform	MAME (Official Binary)
Assigned To	aaron	Resolution	Fixed	OS	Windows XP/Vista 64-bit
Status [?]	Resolved			Driver
Version	0.124a	Fixed in Version	0.124u3	Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	01691: Various Sets: when exiting a game, seems to be any game I get an eip error
Description	I am running vista 64bit sp1 (ultimate if it matters) and if I type say vmame64 pacman the game will load just fine and play but when I am done playing and press escape the cmd box throws up an eip=XXXXXXXXXXXXX(number changes everytime): ACCESS VIOLATION while attempting to read memory at XXXXXXXX. Usually it is 00000000 or FFFFFFFF but not always. It doesn't seem to affect the game itself really but makes me curious. Also if I just type vmame64 and let it bring up the random list of games, chooose one, and then press enter it instantly closes and throws up that eip error. One more thing. In the 64bit builds when I am trying to assign buttons it is very, very laggy and even freezes occasionaly. I've tried mamepp and other 32 bit builds and they don't give that error or have any real problems that I've seen.
Steps To Reproduce	run any game from the command line and then exit. Alternatively just run vmame64 without a game specified and then try to play a game.
Additional Information	sorry if it isn't the right category and such and/or if I should have but the other stuff in seperate bug reports. I am not really sure about where to put it and about filing too many.
Github Commit

Flags	64-bit specific
Regression Version
Affected Sets / Systems	Various Sets

Attached Files

No.00624 Tafoid Administrator Apr 9, 2008, 19:03 edited on: Apr 9, 2008, 19:04	I cannot test this as I don't have a 64-bit system. If someone on Vista/XP-64 bit or even SDLMAME (64-bit) can test this - that would be helpful. It does not reproduce on 32-bit build/32-bit system as reported by OP.
No.00627 user247 Apr 9, 2008, 22:31	Thank you for the fast reply, I've done some more testing and it seems that if I don't have my controller turned on that it doesn't error. I have wireless xbox 360 controllers hooked up using the wireless gaming reciever. So something to do with the controller driver and x64/vista?
No.00628 Tafoid Administrator Apr 9, 2008, 23:10	It's certainly possible. In general, if a driver works in Windows and is detected/functions properly in a control panel joystick test - it 'should' work in MAME. Given it's exclusive to 64-bit, it might be a something that can be corrected (something not compiling correctly). We'll keep this open to allow some more testing and input from other 64-bit users and devs.
No.00637 Mr_Person Tester Apr 12, 2008, 21:48 edited on: Apr 12, 2008, 21:49	I'm getting this intermittently on XPx64. It's infrequent enough that I can't pin down whether or not joysticks have anything to with it, but I don't have a 360 controller.
No.00641 aaron Developer Apr 14, 2008, 00:26	This never happens for me under Vista 64-bit
No.00642 user247 Apr 14, 2008, 02:55	is there anything I can do to help you diagnose it from my end since it doesn't happen to you aaron? I've narrowed it down for sure to it being when my controllers are turned on, I do use them for playing mame. They are wireless xbox 360 controllers using the wireless gaming reciever. No error occurs on the 32 bit version on the same machine.
No.00643 user247 Apr 14, 2008, 03:50	oh and the error doesn't occur until I quit playing as far as I can tell, or maybe mame doesn't update the command line until exiting. The reason I say it doesn't occur until I quit is that sometimes when its quitting I can see the command line without the error and then a second later it shows the error and then give the play time and the emulation speed. It will straight up not even play a game if I start mame without specifying a game and then choose one using the list that comes up, it just quits immediately.
No.00645 aaron Developer Apr 14, 2008, 16:50	Oh, if it has to do with the controllers, then I should have fixed the problem in 0.124u2. There was an incorrectly-sized buffer that only got trashed if you had a controller connected.
No.00647 user247 Apr 14, 2008, 19:04	sweet thanks I'll give it a try later and see