[Lazarus] Memory leak hunt request

Reinier Olislagers reinierolislagers at gmail.com
Sun May 4 15:44:17 CEST 2014


On 04/05/2014 15:37, zeljko wrote:
> On 05/04/2014 02:42 PM, Reinier Olislagers wrote:
>> On 03/05/2014 23:23, taazz wrote:
>>> On 5/3/2014 3:47 PM, Reinier Olislagers wrote:
>>>> On 03/05/2014 14:29, taazz wrote:
>>>>> On 4/26/2014 12:31 PM, Reinier Olislagers wrote:
>>> Find attached a visual aid for correcting the leak. I was expecting some
>>> harder to tell you the truth.
>> Is that the only one you found? Yes, that one is clear and simple
>> enough. Hmmmm, yes, I was expecting something harder as well - something
>> to do with creating visual controls and not cleaning up ;)
>> Thanks for the research!
>>
>> I suppose what I am a bit baffled by is that you can see the property
>> access via fList.Text but the call stack does not show you the actual
>> call (fList:=TStringList.Create) that creates the memleak...
>>
>> Fixed in commit 812cff404faf35b86473eb317b3beb9fc359bf2c
> 
> Would be nice to see svn revision number, instead of that hex sausage :)

Don't blame me, blame git ;)




More information about the Lazarus mailing list