Tony Jackson
09-Jan-2008, 05:56 PM
Hello,
I am using Eureka Log 6x with Delphi 2005. I was memory leak checking an
application that uses Indy SNMP control which uses the IdComponent pas file.
In the initialization/finalization section it reads:
================================================== =======
initialization
GStackCriticalSection := TCriticalSection.Create;
finalization
// Dont Free. If shutdown is from another Init section, it can cause GPF
when stack
// tries to access it. App will kill it off anyways, so just let it leak
// FreeAndNil(GStackCriticalSection);
================================================== =======
This causes a small memory leak of 28 bytes which is reported by Eureka Log
to the in the project's dpr at the "begin" line.
Interesting that the words "so just let it leak" is used by Borland. In
know that this is an Indy product, but it is now a standard part of the VCL.
I also know that this is not the responsibility for Eureka Log to isolate,
but it would be nice (and probably not practical) if these types of
"accepted" leaks could in fact be isolated from the report.
Here is to wishing.
Tony Jackson
I am using Eureka Log 6x with Delphi 2005. I was memory leak checking an
application that uses Indy SNMP control which uses the IdComponent pas file.
In the initialization/finalization section it reads:
================================================== =======
initialization
GStackCriticalSection := TCriticalSection.Create;
finalization
// Dont Free. If shutdown is from another Init section, it can cause GPF
when stack
// tries to access it. App will kill it off anyways, so just let it leak
// FreeAndNil(GStackCriticalSection);
================================================== =======
This causes a small memory leak of 28 bytes which is reported by Eureka Log
to the in the project's dpr at the "begin" line.
Interesting that the words "so just let it leak" is used by Borland. In
know that this is an Indy product, but it is now a standard part of the VCL.
I also know that this is not the responsibility for Eureka Log to isolate,
but it would be nice (and probably not practical) if these types of
"accepted" leaks could in fact be isolated from the report.
Here is to wishing.
Tony Jackson