This thread about [WayBack] DCEF3 memory leak in Delphi XE2 – Alberto Paganini – Google+ taught me that madExcept has a much more elaborate memory leak checking than FastMM4: it checks any Windows memory heap allocation, handle leaks, etc, not just the Delphi code induced memory allocations.
Thanks David Heffernan for commenting this part:
The madExcept leak tracking tools are much more comprehensive than those of FastMM because have much greater coverage. FastMM’s leak tracking tools are great, but only track native Delphi allocations. With the madExcept tooling you get all heap allocations (including non-native ones), handle leaks etc.
That is not to belittle the FastMM tooling at all…
Time to again look at [WayBack] madshi.net – madExcept description
–jeroen