[Lazarus] Memory leaks

[José Mejuto]

El 23/11/2012 12:46, Antonio Fortuny escribió:
>
>
> Le 23/11/2012 12:37, José Mejuto a écrit :
>> El 22/11/2012 14:48, Antonio Fortuny escribió:
>>
>> Hello,
>>
>>> Call trace for block $001EA898 size 28
>>>    $0060787C  IDSTACK_init,  line 937 of
>>> D:/Programmes/LazPk/Indy10_5_8/Lib/System/IdStack.pas
>>
>> This is clear ;)
> Obviously and it is known memory leak
>>
>>>    $0040DBB4
>>>    $004120D1
>>
>> This two may come from Windows OS libraries, or maybe the fpc RTL
>> functions (more probably).
> Annoying but can cope with it

Just to be sure you can load your project and run procexp (process 
explorer) which could show you the base address for the loaded DLLs, 
quite sure one would be loaded in the "00400000" address, which is the 
path to arrive the offending function (maybe sockets related).

>>>    $BAADF00D
>>
>> This comes from an already freed object (BAD FOOD), so the first step
>> could be to change all object.free by FreeAndNil(object).
> Ouaou ! This means a lot of search !

Not that much, but the problem is that many code runs fine due that bug, 
using a freed object (not intentionally). Maybe some regexp replaces 
will help you.

You can review only code that deals with Indy activities.


--