GroovyMame crashing - unhandled st11logic_error exception

[MtothaJ]

I often get the following crash when running GroovyMame:

Caught unhandled St11logic_error exception: basic_string::_M_construct null not valid

Usually what also happens is that in game the game would freeze up for a moment before continuing on.

Any ideas on this?

[haynor666]

I had the same problem on XP x32 when I start mame without any game. No problem if I start mame.exe [game]

Check latest GIT, might be already fixed (if it's official mame problem).

[MtothaJ]

I get this regardless of whether I go in through the mame executable or straight into a game via the command line.

THe game freezes and stuttering can be heard. It would then resume as normal only to freeze up again in a few moments.

[MtothaJ]

I seemed to have resolved my problems with stuttering / momentary freezes in games by enabling triplebuffer and multithreading. I also have vsync on.

I still get the unhandled st11logic_error exception from time to time when exiting Groovymame but that is not a big deal.

[Calamity]

I seemed to have resolved my problems with stuttering / momentary freezes in games by enabling triplebuffer and multithreading. I also have vsync on.

I still get the unhandled st11logic_error exception from time to time when exiting Groovymame but that is not a big deal.

I remind getting that error, last month or so, I'd say it got fixed when updating the whole MAME folder from baseline.

Multithreading/triplebuffer is a compromise setup that should only be used when the target refresh is not achieved or the cpu can't keep up with emulation.

[MtothaJ]

I seemed to have resolved my problems with stuttering / momentary freezes in games by enabling triplebuffer and multithreading. I also have vsync on.

I still get the unhandled st11logic_error exception from time to time when exiting Groovymame but that is not a big deal.

I remind getting that error, last month or so, I'd say it got fixed when updating the whole MAME folder from baseline.

Multithreading/triplebuffer is a compromise setup that should only be used when the target refresh is not achieved or the cpu can't keep up with emulation.

The CPU I am using is a Pentium G4400 (2 core 3.3Ghz, 1151 Skylake socket). I would think that this should be sufficent for MAME however I intend to upgrade the CPU in the future and when I do I will post back whether the stuttering / freezing is resolved using the standard settings.

In any case, since I am using the ASIO sound I understand that Multithreading should be left on regardless.

[Tetsuo1981]

Bumping his thread cos I've received this error on normal, groovy and UI versions of mame all with the same error message on 2 PC's running different versions of windows. Only happens when I try to quit back from a game to the game select screen and only when I use my joystick setup button combo, using the keyboard everything works fine. Googling the error throws up notuch related to mame and loads about other programme. Anyone got any ideas or solutions?

Cheers

[haynor666]

https://github.com/mamedev/mame/issues/1778