I encounter the same error with 32-Bit MAME.EXE v0.179 or v0.180 under Windows 10:
romset goindolu [goindol] is good romset goinnuts is good Caught unhandled St9bad_alloc exception: std::bad_alloc
Those ROMs are OK, this must be an issue with MAME or Windows.
Interesting fact: While doing a little research I found a problem I have with old MAME v0.53: This rises error while doing single ROM audit:
X:\MAME>mame -verifyroms vsavh ----------------------------------------------------- Exception at EIP=007BACB5: ACCESS VIOLATION While attempting to read memory at FFFFFFFF ----------------------------------------------------- -> Problem was a Carriage Return in MAME.INIs rompath-line where my rompath was really on the next line in MAME.INI.
So now I deleted MAME.INI on my actual MAME 0.180 and when I now run a complete ROM audit with -verifyroms * I get the error later with:
romset travrusa is good romset travrusab [travrusa] is good Caught unhandled St9bad_alloc exception: std::bad_alloc
Index 
Flat 
Re: mame 0.171 -verifyroms does not always work
Reply
