In some cases, it seems that mmosOptimizeForSpeed can cause memory leaks in anonymous methods

[Leewx820]

I compiled the same program using mmosOptimizeForLowMemoryUsage and mmosOptimizeForSpeed. The program using the mmosOptimizeForLowMemoryUsage option does not have continuously increasing memory usage, while the one using mmosOptimizeForSpeed has memory usage that keeps increasing at certain times. I did not capture any memory leak logs when the program exited, even with memory leak checking enabled. This issue has been troubling me for a while

[pleriche]

The differences between the optimization strategies is not large. When optimizing for low memory usage the internal fragmentation will typically be slightly lower, but it is not a night and day difference. You'll see this in a lower commit size for the process, and if you obtain the memory usage stats the overhead percentage may also be somewhat lower.

The optimization strategy cannot affect the state capture - that just reports everything the application has allocated. Are you sure you're comparing apples to apples here, and there's not perhaps some other setting in your application that you're changing at the same time that causes it to allocate more of the objects you highlighted above?

[Leewx820]

I have only compared the differences between the two strategies so far, and I cannot determine the exact cause yet. I will continue to check the code