Enable/Disable Memory Leak detection at runtime?

[waeberd]

Hi,

just evaluating EurekaLog and I am impressed!

One question: is it possible to enable (and eventuelly disable) Memory Leak detection at runtime?

I can imagine that memleak detection should run from the beginning, so an activation by commandline switch when launching the delphi project would be fine too.

All I could find in the documentation was the LeaksOptions property (class TEurekaModuleOptions), but this is a readonly property.

Would be great to get an answer.

Again, congrats for this great product!

Best regards, Daniel

[admin]

Hi,

this is an interesting feature (the parameter command)!

I think to add it in the next 6.1 version.

Currently is impossible to do, I'm sorry.

[waeberd]

I think to add it in the next 6.1 version.

Thank you for picking up this feature request Fabio!
Order has just been submitted.... waiting for the download link! :)

Thanks, Daniel

[admin]

Hi,

you're welcome! :)

[Unregistered]

Hi,

This is an interesting idea. We get a memory leak on shut down of all our applications due to the Indy components (deliberately) not freeing resources. It gets quite annoying and it's easy to just close it down without inspecting it properly, so would be nice if there was some way to show only our leaks that we may have introduced and not the Indy ones.

Some kind of exclude list might be possible, perhaps?

[admin]

Hi,

I'm working on, please to be patient (a bit more)! :)

[TNT]

FastMM4 has a leak exception method RegisterExpectedMemoryLeak(..) that would be REALLY nice to have in Eureka Log.

[admin]

Really interesting.

I'll study it shortly! ;)

[Piotr Rezmer]

We get a memory leak on shut down of all our applications due to the Indy components (deliberately) not freeing resources. ...
Some kind of exclude list might be possible, perhaps?

Hi, I vote for this too, because I get mail with exception every time when application is closed.

|0056ECC1|CTIServer.exe|IdComponent.pas| |Initialization |185[1]|

:)
best regards
Piotr Rezmer

[admin]

OK, I have understand! :)

[PekunZip]

OK, I have understand! :)

... is enabling/disabling memory leak detection at runtime possible now?

[admin]

Hi,

not even, but I'm working on, please to be patient (a bit more) :)

[Unregistered]

Hello.

2 All:
Eventually, there is only one admin. He haven't unlimited time to implement ALL of the "I want" from us.
I think if you'll dedicate some of your time to research and developing the problem, you can provide an sample code for wanted feature.
Chances of sooner implementation are higher with some samples, so admin can more easily and quickly comes up with the solution.
If your wanted feature is at the bottom of TODO list and you do not want to wait, then you can implement it by yourself (of couse it means, that you'll need source code). Then you can send ready implementation to admin for integration with current build of EL. And, well, your code must be a good quality code. No point to inject "bad" code to EL.
If you do not want to spend your time developing a solution then the only option is to wait. All features will be implemented sooner or later (well, maybe except the most insignificant).

[admin]

Hi,

yes this is a really good suggestion, thank you very much! :)