Alberto Paganini 3 Posted August 29, 2020 I use FastMM4 to check memory leaks and I noticed the report file " MyApplicatoin+MemoryManager_EventLog.txt" is not deleted automatically once I have amended the source and I run my application again. This way if there are still memory leaks they are added to the existing report and this confuses me. Is there an option in FastMM4 to achieve that I am not aware of or do I have to rely on DeleteFile(...) when I run the application ? Many thanks Alberto Share this post Link to post
David Heffernan 2353 Posted August 29, 2020 It's automatically deleted here. Try setting up a brand new app and check how it behaves there. Share this post Link to post
Alberto Paganini 3 Posted August 30, 2020 Quote It's automatically deleted here. Try setting up a brand new app and check how it behaves there. I did and created this test: program Project3; {$APPTYPE CONSOLE} {$R *.res} uses FastMM4, system.Classes, System.SysUtils; var t:tstringlist; begin t:=TStringList.Create; end. I ran it a number of times and the new reports are appended to the old ones. Obviously there must be something wrong in my FastMM4 settings. I will look into that. Share this post Link to post
David Hoyle 68 Posted September 4, 2020 This can be changed via the FastMM4Options.inc file if I remember correctly (sorry not a a development machine to be more precise) and possible with directives defined in the project. The settings is {.$define ClearLogFileOnStartup} looked up the inc file on GitHub. 1 Share this post Link to post
Alberto Paganini 3 Posted September 5, 2020 21 hours ago, David Hoyle said: This can be changed via the FastMM4Options.inc file if I remember correctly (sorry not a a development machine to be more precise) and possible with directives defined in the project. The settings is {.$define ClearLogFileOnStartup} looked up the inc file on GitHub. Thank you David, this did the trick ! Share this post Link to post