Jonas wrote: > export MallocStackLogging=1 > Then, once the program is running and has leaked memory, run > leaks nameofyourprogram
Thanks for this tip! It is very interesting, however in this situation it does not detect the lost memory. At this point I have to give up on GetTextWidth - I will avoid it for now. Maybe next year the problem can be solved. I will send a note to the Lazarus list and submit a bug report, provided I can confirm the issue with a minimal testing program. Cheers, Tobias _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
