MAMEWorld Forums - Programming - Re: Memory leak when compiling the emumem files.

> My test results from compiling Mame do not lie. The memory leaks at those emumem
> files were always consistent every time I compiled mame.

You’re using terminology incorrectly. It is not a “memory leak”, compiling those files just requires a lot of memory.

> If those leaks do not happen from your end, then I am for sure curious. In the
> meantime, I will have to allocate more storage device memory to ram or compile with a
> small amount of cc1plus files; -j2 is the max for now.

Take a step back here. The code was migrated to C++17 about a month ago. Which of the following scenarios is more plausible?

No-one can compile MAME, the successful GCC builds on GitHub Actions are faked, and we’ve gone through the motions of a month of development and subsequent release preparations for shits and giggles.
We can all compile MAME just fine, and the compiler failing to allocate memory really is caused by a 32-bit compiler running out of addressable space.

There is no way what you’re saying is correct. On a system with at least 8GB of available RAM/swap, a 64-bit version of GCC or clang will not fail to allocate memory building any of MAME’s source files. The errors you are describing only happen with 32-bit compilers, and even then the 32-bit version of GCC10 can successfully compile MAME.

You’re the one with the issue here, yet you’re trying to tell the people who can compile MAME successfully that they don’t know what they’re talking about.