Speicherleck und Unknown Elemente in FastMM4

[Kas Ob.]

Hi,

Not every memory leak can be classified as known, or simply named, for example try a simple GetMem without FreeMem and see for yourself.
I suggest FastMM4 in full debug mode that will generate a detailed report with extended stack to the call that caused the allocation, so you can find on your the missed part of the code to free that allocation (or the class/object ...)

Start with FastMM4 FullDebug version and read a/the report after simple leak in simple new project, from there you can test your application, in other words get familiar with the Call stack and memory leak report first.

Or use EurekaLog, MadExcept...