Root > Compatibility > 5.x -> 6.x > EurekaLog 6 Documentation > Memory Leaks Limits

Memory Leaks Limits

Previous pageReturn to chapter overviewNext page   

Caution: this is old EurekaLog 6 documentation. This is not the latest version.


The EurekaLog Memory Leaks Detection has same limits derives from its internal structure.


EurekaLog detects the memory leaks at the program exit, so at this state the program has just freed all its non-static resources (resources allocated at run-time as Object created with the Create method, variables allocated with the GetMem function, or constants arrays).


This technique generating the following limitations:



1.        currently this feature is available only in Delphi (not C++Builder);


2.        the Leak report automatically hide the Assembler and CPU sections;


3.        during the Leaks handling EurekaLog did not execute its events (this because all the needed memory resources are just freed);


4.        a little performances decreasing (no more that about 5%);


5.        a little memory usage increasing (about 300 bytes for every memory allocations);
6.        EurekaLog can catches a max of 1024 leaks (to avoid the creation of a too BIG report file);


7.        EurekaLog isn't able to catches memory leaks in projects compiled with Run-Time Packages.




It's possible customize the EurekaLog options, related to the Leaks detection, before the program exit (using an unit "finalization" section, a TForm.OnDestroy event, or just putting it at the end of the project source code).




program Project1;




  ECore,  // Needed unit

  ETypes, // Needed unit


  Unit1 in 'Unit1.pas' {Form1};


{$R *.res}




  Application.CreateForm(TForm1, Form1);



  // EurekaLog customization (for the Leaks Detection)...

  CurrentEurekaLogOptions.EMailSendMode  := esmSMTPServer;

  CurrentEurekaLogOptions.EMailSubject   := 'BUG Report';

  CurrentEurekaLogOptions.EMailMessage   := 'This is a BUG Report.';

  CurrentEurekaLogOptions.EMailAddresses := '';


Send feedback... Build date: 2022-01-17
Last edited: 2018-06-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: