Ignore Indy memory Leak

[Christian]

Hello,
I'm evaluating to buy EurekaLog, I have 2 problems at the moment.

a) Indy reports 1 memory leak each time I close the application (I need to ignore it). It would be usefull to have an event where we can determine if a memory leak should be ingnored.

b) I need to set the error log zip file name at run time.

[admin]

Hello,
I'm evaluating to buy EurekaLog, I have 2 problems at the moment.

a) Indy reports 1 memory leak each time I close the application (I need to ignore it). It would be usefull to have an event where we can determine if a memory leak should be ingnored.


I think to implement this shortly! :)


b) I need to set the error log zip file name at run time.


Use these command:

CurrentEurekaLogOptions.OutputPath := 'LogFileName.elf';

[Andrew Ryals]

Is there a work-around to the "a" part of this post? I am EL v 6.0.5

Andrew

"admin" <support@eurekalog.com> wrote in message
news:admin.2p8cib@no-mx.news.eurekalog.com...
>
> Christian Wrote:
>>
>> Hello,
>> I'm evaluating to buy EurekaLog, I have 2 problems at the moment.
>>
>> a) Indy reports 1 memory leak each time I close the application (I need
>> to ignore it). It would be usefull to have an event where we can
>> determine if a memory leak should be ingnored.
>>
>
> I think to implement this shortly! :)
>
>>
>> b) I need to set the error log zip file name at run time.
>>
>
> Use these command:
>
> CurrentEurekaLogOptions.OutputPath := 'LogFileName.elf';
>
>
> --
> admin
>
> Best regards...
>
> Fabio Dell'Aria.
> ------------------------------------------------------------------------
> admin's Profile: http://news.eurekalog.com/member.php?userid=1
> View this thread: http://news.eurekalog.com/showthread.php?t=749
>

[admin]

I'm working to add this new feature, in the mean time why not write to the Indy Team to fix this leak? :)

[RichB]

I understand that this may be a Indy problem, but this is an older Delphi7 source so I am not sure it is safe to change.

MemCheck did not report it, so it may have ignored it.

I hesitate to change this code:
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);
end.

Can this be ignored?

- Rich

[admin]

Hi,

you can try to uncomment this code and just see what appends!