Pierre le Riche

Sounds like a good feature to have. I'm swamped with other work for the foreseeable future, but you're welcome to take a shot at it. :)

Hi Wesley, What you're seeing is most likely the effect of an earlier memory pool corruption (most often a buffer overrun). Please try enabling debug mode (call FastMM_EnterDebugMode on startup)...

Ok, so what is likely happening here is that the application is still attempting to use blocks (perhaps objects) after it has freed them. It could also just be due...

Hi Vladimir, I've added a couple of ifdefs in order to suppress the spurious warnings under Delphi 10 Seattle. Please confirm that it resolves the issue for you. Thanks, Pierre

Hi Vladimir, apologies, that should now be fixed.

Thank you, Olivier. I have made the change in the repository.

If I were to rename AMinimumAllocationGroup and AMaximumAllocationGroup to AAddFromAllocationGroup and AAddUpToAllocationGroup, and then also add ASubtractFromAllocationGroup and ASubtractUpToAllocationGroup parameters, would that help? The idea is that allocations in groups...

I have pushed this addition to the repository.

If I understand correctly what you want to do, then I believe these are the settings you should use: ``` AAddUsageInAllocationGroupsFrom = 0 AAddUsageInAllocationGroupsUpTo = FastMM_CurrentAllocationGroup ASubtractUsageInAllocationGroupsFrom = 0 ASubtractUsageInAllocationGroupsUpTo...

Hi Hans I've never considered adding the detail to the usage report, because generally it would be a massive report and would be difficult to parse, Even the "differential" usage...