[Lazarus] Memory leak hunt request

Reinier Olislagers reinierolislagers at gmail.com
Sat Apr 26 12:08:52 CEST 2014

On 26/04/2014 12:08, Graeme Geldenhuys wrote:
> On 2014-04-26 10:31, Reinier Olislagers wrote:
>>From my experience, develop your software from the ground up with
> Heaptrc unit enabled (compiler option -gh). It is MUCH easier to fix a
> memory leak the second you created it, compared to 6 months down the line.
Yes. I know. Did you read my post ;) ?

> As for your question about how to resolve them. Simply enable -gh, run
> your app from a console window. Start simple. eg: Run the app, then
> immediately exit. Do memory leaks occur? If so, analyse the heaptrc
> output. Trace the line numbers and call stack. Go through the affected
> code with a fine tooth comb. Fix and repeat the test. Did the leak count
> reduce.
Yes, I ran leakview. Apparently it wasn't clear I'm asking for help
diagnosing and fixing the remaining leaks....

More information about the Lazarus mailing list