[Lazarus] Memory leak hunt request

[taazz]

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:
>>> There are still quite some leaks present, and I'd appreciate comments on
>>> what exactly to fix to get rid of them...
>> 1) any steps to reproduce the leaks?
>>      I did run the application with trace enabled and upon exit no memory
>> leaks where reported, after that I played with it a bit creating a
>> couple of table views and stored procedures but I didn't get any leaks
>> reported other.
>> When I say I got no reports I mean that the leak file (opened it from
>> the leakview utility) was empty.
> Sorry if I didn't mention that: right-click on a table, select view
> first 1000 rows gives the leak.
> I'm interested in finding out how to solve this one and hopefully I can
> learn from it.
> (Fairly GUI/Laz newb here - no Delphi background).
Find attached a visual aid for correcting the leak. I was expecting some 
harder to tell you the truth.
> An additional issue on Windows seems to be views/right click on a view,
> Display View DDL gives error message Failed to create win32 control,
> error 0: the operation completed succesfully...
> MSDN indicates this can happen if a CreateWindowEx procedure failed;
> searching forum gave a hint about message hooks being used (which I
> suspect does not occur here); mailing list gave a suggestion that memory
> was corrupted leading to this problem.
from a quick look around I can't see any problems and it is in a part of 
the lcl that I never payed any attention so this will take longer, and I 
need to put it in my todo. I'll try to push it up the list but I can't 
promise anything at this time.
> <snip>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: leak.png
Type: image/png
Size: 82125 bytes
Desc: not available
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20140504/8fe6ee29/attachment-0003.png>