AM non-responsive (Screen saver issue ?)

[jimmer]

On my system (winXP on core2duo, calling MAME.) there is something weird with exiting MAME back to AM, it seems to hang for 2 or 3 seconds sometimes before it will accept inputs.

I think the screensaver might be involved, it might activate in background while you are playing a game. Just now when I exited a game I found myself in the AM screensaver, and it wouldn't come out of screensaver when I pressed buttons (it did after about 10s of pressing buttons).

anyone else found this, or got any thoughts?

My screensaver is the default one, showing the snaps, all the options set to No/None.


edit:
I tried disabling the screensaver by setting the timer to 0. And that caused AM not to accept inputs when I exited a game. I could open task manager but when I went back to AM it was still not responding to inputs.

[jimmer]

I'm finding it hard to get any repeatable pattern.  Sometimes I get the games list and non-responsiveness for a second or two, and sometimes it stays non-responsive. Other times I exit the game into the AM screensaver which is usually unresponsive for about 20key presses.  Sometimes there is no proble.

There is a time element, which I'm guessing is related to the last time a button was pressed. I've never seen it go wrong if I have just finished a game. The chance of it going wrong seems to increase the longer the MAME game has been left running.

I've gone back to version 1.5.3 now, and so far I've not had a problem.


Should I enter a bug report ?

[Snorlax]

I'm seeing a similar issues, latest AM, latest RetroPie on R3.  Essentially I end a game, it goes back to the AM screen and but no input is accepted.  What I noticed though was runcommand from the previous game was still active; killing runcommand brought back control to AM.

For the moment I've stopped using runcommand and am running the emulator directly, no issues.