You could put a break point in the destructor for the TInterfacedObject
descendant and if it doesn't get called (which it sounds like it's not)
then you know that you still have something, somewhere, referencing it.
Cheers,
Phil.
Dennis Chuah wrote:
Works for me all the time. The object sis freed when the reference
count reaches 0. Check for circular references.
The number of handles in task manager is all handles, process, thread,
file, duplicate, etc. that are opened/created by the process.
----- Original Message ----- From: "Rohit Gupta" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "NZ Borland Developers Group - Delphi List"
<[email protected]>
Sent: Thursday, May 05, 2005 9:47 AM
Subject: [DUG] TInterfacedObject
TInterfacedObject
Am I right in concluding that any descendant will be reference
counted and the memory released automatically ?
I an a particular very small app, this doesnt appear to be the case.
Every time it handles a transaction the memory goes up by 60K and
the handle count by 8.
Next question, what is this handle count in the task manager ? Is it
file handles, process handles ????
Regards
Rohit
====================================================
==================
CFL - Computer Fanatics Ltd. 21 Barry's Point Road, AKL, New
Zealand
PH (649) 489-2280
FX (649) 489-2290
email [EMAIL PROTECTED] or [EMAIL PROTECTED]
====================================================
==================
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
