Tim,

A memory leak has suddenly appeared in my application when opening one of my tables.
The leak was first reported by FastMM4.

Please find attached the Sleuth CodeWatch Analysis Report.  

The last line of my code in the memory leak report is:
mctx70cx.exe Imaputil.pas line 25918 (Imaputil::ApplyRelationRules + 0CAh)

Above that are codes related to DBISAM.

I am using DBISAM 4.27 Build 1 with Delphi 5 SP2.

Regards,
KK Aw

KK


You say "opening one of my tables" so presumably there are others which don't have a memory leak? If so what is different about the table that does have the leak, and what is different about the operations you are performing on it?

Roy Lambert [Team Elevate]

Roy,

Yes, there are other tables that were opened that did not register a
leak.  I have verified the table and even replaced it but the leak is
still reported.

It is opened for reading inside a transaction.  Other than that, I have
not figured out what is happening.

KK Aw

kk


I've never used Sleuth CodeWatch can you generate the FastMM report?

You need to add something like

 FastMMDebugSupport in 'C:\3rdParty\FastMM\Replacement BorlndMM DLL\FastMMDebugSupport.pas',

in the dpr uses clause and

ReportMemoryLeaksOnShutdown := DebugHook <> 0;
SetMMLogFileName(PChar('C:\zap\Leaks.txt'));

just after the begin in the dpr

Roy Lambert [Team Elevate]

ps How do you pronounce your name? <vbg>

<< A memory leak has suddenly appeared in my application when opening one of
my tables. The leak was first reported by FastMM4.

Please find attached the Sleuth CodeWatch Analysis Report.

The last line of my code in the memory leak report is:
mctx70cx.exe Imaputil.pas line 25918 (Imaputil::ApplyRelationRules + 0CAh)

Above that are codes related to DBISAM. >>

Does the FastMM leak occur when you open the table using DBSYS ?

Can you email me a copy of the table ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Copy of table attached.
Opening the table by itself does not leak.

ApplyRelationRules is inside a transaction and it is called several times.

In ApplyRelationRules I use tdbisamtable.create and free.  Could this be
causing the problem?  I will try to add a table component in my
datamodule and see if the leak still occur.

I think this problem only happen after I upgraded to 4.27.  I am working
with very old codes.

KK Aw


Tim Young [Elevate Software] wrote:
> << A memory leak has suddenly appeared in my application when opening one of
> my tables. The leak was first reported by FastMM4.
>
>  Please find attached the Sleuth CodeWatch Analysis Report.
>
>  The last line of my code in the memory leak report is:
>  mctx70cx.exe Imaputil.pas line 25918 (Imaputil::ApplyRelationRules + 0CAh)
>
>  Above that are codes related to DBISAM. >>
>
> Does the FastMM leak occur when you open the table using DBSYS ?
>
> Can you email me a copy of the table ?
>
> Thanks,
>

Tim,

After I stop using TDbisamTable.create on the fly, the memory leak went away.  This is a
work around for now.  
I have used Tdbisamtable.create in many places so it would be good if the problem can be
address at the dbisam level.  

KK Aw

Corrections.  FastMM is still reporting memory leak.

I have to remember that I cannot use FastMM and Sleuth Codewatch together!

KK Aw

One of my scheduled procedure will now freeze the application.  For now
I need to revert back to the last build of version 4.26.  Where can I
download it.

HELP!

KK Aw

<< One of my scheduled procedure will now freeze the application.  For now I
need to revert back to the last build of version 4.26.  Where can I download
it. >>

As I said via email - 4.27 has nothing to do with that.  If you look at the
changes between the two versions, you will see very little at all has
changed:

http://www.elevatesoft.com/incident?action=reported&category=dbisam&release=4.26&type=F

Did you change anything recently in your application ?

--
Tim Young
Elevate Software
www.elevatesoft.com