Compile out expensive debugs from Debug configuration

[xezon]

Right now, Debug is abysmally slow on game boot. Identify slow debugs on load and frame and gate them behind cmake options. An obvious offender is MEMORYPOOL_DEBUG, that collects stack traces on pool creation, and stalls the application boot for minutes.

[Mauller]

This was causing me nothing but pain when trying to test that the asm changes did not break debug.

Sometimes the game would not even load and just hanged in the memory test.

[Mauller]

i think this can be considered closed now after your memory manager cmake config commit.

[xezon]

Is debug speed acceptable compared to Release?

[Mauller]

Yeah it's perfectly acceptable, i don't notice a difference as long as the game memory manager debug stuff is kept minimal.

The only issue i do see is the games memory usage expanding by megabytes every few seconds, after a few minutes the debug run can easily balloon to over 1GB. But in normal operation this doesn't happen.

Also when using the null memory implementation under debug the above doesn't happen, so i think there is something being compiled in with the debug flags on the memory manger that has a significant leak.

[xezon]

Perhaps you can narrow down the source of the leak by trying different MEMORYPOOL debugs.

[Mauller]

Perhaps you can narrow down the source of the leak by trying different MEMORYPOOL debugs.

Memory Checkpointing appears to be the thing making memory balloon over time.
Disabled it this morning and the memory remained stable.

Not looked internally at it yet though.