> Something within Mame's code is causing cc1plus.exe to memory leak when it compiles > at the emumem files (at least on my end). It shouldn't have to use >10 GB of ram just > to compile Mame.Didn't mean to say 10GB b/c that was from compiling under -j5. > > So the "j" setting from my examination determines how much instances of cc1plus are > used when compiling Mame. I decided to check memory behavior for only one cc1plus > instance and the memory used for this application just kept rising until it was > finished with an emumem file. Highest I seen it go up to so far was about 5 GB of ram > used compiling emumem_mview.cpp. > > What I did was use Resource Monitor to inspect cc1plus.exe's memory usage. Wait until > cc1plus compiles the emumem files and watch the ram usage rise. > > Edit: Seems to be a known issue: > https://github.com/mamedev/mame/commit/5...891bc1008ed94.. > Going to have to compile with two cc1plus instances "-j2" until this bug is fixed for > good.
I can compile with -j40 on 16GB if I want, Windows will just use swapfile, it takes much longer that way, and thrashes the disk like hell, but no out of memory.
If you're trying to use a 32-bit environment or something, keep in mind that's no longer officially supported, and on the machine you have, there's no reason to do that.
|