Pierre le Riche

Hi Eric, I don't have any bug reports for the UseReleaseStack feature, but it is fairly new so there is always the possibility that there is some rare race condition...

Hi Mitch, Runtime adjustment of the number of arenas is on the to-do list. The plan is to allocate the arena management structures instead of using gobal variables for them....

Those percentages are quite small. I fear that the additional costs of dynamic management of arenas might counter any gains to be had. However, I will see what I can...

Hi Mark, FastMM5 does not use the FastMM4Options.inc file, since the {$include} directive would raise a compiler error if the file was not present (which is usually the case). In...

> Here's the first one I noticed missing, ClearLogFileOnStartup Thanks, I've pushed a fix for that.

Thank you for the bug report. I have encountered this before, but luckily the worst case scenario (silent memory corruption) is not a scenario that arises frequently - an FPU...

Hi Jaclas, _On the Praxis forum you said that nobody needs a long call stack, that in practice a shorter one is enough._ I didn't put it in such strong...

Hi Jaclas, I have added support for configuring the depth of the allocation and free stack traces runtime. The minimum value is 0 (if you're tight on memory or you...

Hi, You need to add either the backward compatible `ReportMemoryLeaksOnShutdown := True;` or the FastMM5 specific ` FastMM_MessageBoxEvents := FastMM_MessageBoxEvents + [mmetUnexpectedMemoryLeakSummary];` to the DPR. Best regards, Pierre

The FastMM_LogToFileEvents set controls which events are logged to file. The option you're looking for is mmetUnexpectedMemoryLeakDetail. This will log the summary as well as the detail to the log...