As the subject says, happens with 3.111a
Restarting Clrmame helps, but it is annoying ;(

It occurs randomly, so no reliable way to give the exact steps to reproduce it :/

It happens if you got only a little amount of RAM (< 2GB) and you use a datfile which got roms listed which are rather big (like > 1GB). The cause of this is the auto-memory option of the rebuilder, which tries to allocate the biggest current rom-size as ram for the no-recompress functionality.

Turn off the 'auto' option for "memory used for 'no recompress'" in Rebuilder advanced for the given profile. If you can't open it, set "Rebuilder_AutoMemory = off" in the belonging settins/*.cmp file.

I think I should limit the maximum value to 1/2 of the system's ram in the next version.


Roman Scherzer

> It happens if you got only a little amount of RAM ( 1GB).
Nowadays 1GB is "a little amount of RAM"? :P

> The cause of this is the auto-memory option of the rebuilder, which tries to allocate the biggest
> current rom-size as ram for the no-recompress functionality.
>
> Turn off the 'auto' option for "memory used for 'no recompress'" in Rebuilder
> advanced for the given profile. If you can't open it, set "Rebuilder_AutoMemory
> = off" in the belonging settins/*.cmp file.
>
> I think I should limit the maximum value to 1/2 of the system's ram in the next
> version.
>
>
> Roman Scherzer
>

Thanks for the clarifications on that issue. Limiting the value to 1/2 of the RAM seems to be a good decision for us users with "low-end" systems. :)

> Nowadays 1GB is "a little amount of RAM"? :P

Yes...I got 4GB ;)


> Thanks for the clarifications on that issue. Limiting the value to 1/2 of the
> RAM seems to be a good decision for us users with "low-end" systems. :)
>


Yeah...will think about it


Roman Scherzer