Subject | Re: IBO caching |
---|---|
Author | scr0546 |
Post date | 2007-01-19T22:31:57Z |
Yes, Jack is right. FastMM is really easy to use:
1) Place FastMM4 unit as the very first unit under the "uses"
section in your project's .dpr file.
2) In FastMM4.pas set
{$DEFINE LogMemoryLeakDetailToFile}
{$DEFINE FullDebugMode}
3) Copy FastMM_FullDebugMode.dll to the same folder where the
project.exe is compiled to.
After closing your application you will find the memoryleaks (with
stack trace) in a logfile "Project_MemoryManager_EventLog.txt".
I didn't find memory leaks - caused by IBO - in my applications ;-)
Best regards
Joe
1) Place FastMM4 unit as the very first unit under the "uses"
section in your project's .dpr file.
2) In FastMM4.pas set
{$DEFINE LogMemoryLeakDetailToFile}
{$DEFINE FullDebugMode}
3) Copy FastMM_FullDebugMode.dll to the same folder where the
project.exe is compiled to.
After closing your application you will find the memoryleaks (with
stack trace) in a logfile "Project_MemoryManager_EventLog.txt".
I didn't find memory leaks - caused by IBO - in my applications ;-)
Best regards
Joe
--- In IBObjects@yahoogroups.com, "jrodenhi" <jack@...> wrote:
> My application had a bunch of memory leaks
> that all came from two or three non-freed objects, but I could not
> find them until I got into FastMM. Now memory leaks still happen
once
> in a while but they are really easy to find.
>
> -Jack