[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[delphizip] Re: Possible memory leak

I advise caution in this area. It is technically "correct" to unload the DLL
when you are done.  

The "autoload" option was mostly done for backwards compaitibility. It's
best if each program does the load and and unload themselves.

A leak of 200 bytes is not awful anyway. The last time I checked, the VCL
had lots of leaks around this size.  The important thing is to avoid leaking
inside a loop that may be done lots of times. 

But I don't think loading or unloading the DLLs would be done in a loop.

Eric

-----Original Message-----
From: Roger Aelbrecht [mailto:roger.aelbrecht@wanadoo.be]
Sent: Saturday, January 19, 2002 2:40 PM
To: delphizip@freelists.org
Subject: [delphizip] Possible memory leak


Hi,

To solve a bug in my application that uses TZipBuilder, I made CodeGuard
active and this reports
a memory leak of 200 bytes.
When I remove the line with "ZipBuilder->Unload_Zip_Dll();" the memory leak
is no longer reported
Using the autoload function of TZipBuilder CG reports also memory leaks.
Did anyone else detect this problem too, or is it Code Guard playing tricks
with me.
I would like to now if it is a bug in ZipBuilder or not.
If it seems to be a bug I will try to investigate when other jobs are
completed.

Regards
--
Roger Aelbrecht
http://web.wanadoo.be/driehoeksw


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[delphizip] Re: Possible memory leak

Thanks for your advice, I was not doing it in a loop but rather frequenly. I
did the load and unload
"when needed" and noticed some instability after a wghile.
I changed now the application to load the DLL's once at the start of the
application and unload at the
closing. Codeguard still reports the leak but it dos also if I load/unload a
nearly empty DLL.
--
Roger Aelbrecht
http://web.wanadoo.be/driehoeksw
----- Original Message -----
From: <Eric.Engler@zcsterling.com>
To: <delphizip@freelists.org>
Sent: Monday, January 21, 2002 3:21 PM
Subject: [delphizip] Re: Possible memory leak


> I advise caution in this area. It is technically "correct" to unload the
DLL
> when you are done.
>
> The "autoload" option was mostly done for backwards compaitibility. It's
> best if each program does the load and and unload themselves.
>
> A leak of 200 bytes is not awful anyway. The last time I checked, the VCL
> had lots of leaks around this size.  The important thing is to avoid
leaking
> inside a loop that may be done lots of times.
>
> But I don't think loading or unloading the DLLs would be done in a loop.
>
> Eric
>
> -----Original Message-----
> From: Roger Aelbrecht [mailto:roger.aelbrecht@wanadoo.be]
> Sent: Saturday, January 19, 2002 2:40 PM
> To: delphizip@freelists.org
> Subject: [delphizip] Possible memory leak
>
>
> Hi,
>
> To solve a bug in my application that uses TZipBuilder, I made CodeGuard
> active and this reports
> a memory leak of 200 bytes.
> When I remove the line with "ZipBuilder->Unload_Zip_Dll();" the memory
leak
> is no longer reported
> Using the autoload function of TZipBuilder CG reports also memory leaks.
> Did anyone else detect this problem too, or is it Code Guard playing
tricks
> with me.
> I would like to now if it is a bug in ZipBuilder or not.
> If it seems to be a bug I will try to investigate when other jobs are
> completed.
>
> Regards
> --
> Roger Aelbrecht
> http://web.wanadoo.be/driehoeksw
>
>
>


This list brought to you by FreeLists