[Lazarus] Memory leak hunt request

[Reinier Olislagers]

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

>> 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.
No problem - glad to at least know my quick look conclusion corresponds
with yours ;) As always, thanks for any help.

BTW: regardless of its problems, TurboBird can now script an entire
database of mine that FlameRobin refuses to output correctly (it does
not take view dependencies into account).
Currently working on getting the resulting script to run correctly and
generate an identical database. Rinse and repeat, then on to more GUI
issues...

As usual, hints and tips welcome!