No memory leak with free of base class

Hi
Can somebody explain why there isn't any memory leak here ?

type ttest=class(tcomponent)
private
    fa: string;
published
    property a: string read fa write fa;
end;


procedure TFrmMain.Button1Click(Sender: TObject);
var
test: ttest;
begin
while true do
begin
    test := ttest.create(nil);
    test.a := 'errror!';
    tcomponent(test).free;   //<--- no mem. leak here?!?
end;
kogerAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Hagen040798Connect With a Mentor Commented:
First. Each memoryblock allocated by the standard Memorymanager contains before the memoryblock an Integer that storres the allocated size of the Block. This size might be slightly greater than the requested memorysize. On deallocation the MM decrement the Pointer by 4 and get so this Value (called SizeFlags).
Second. For each Class the Compiler store into the codesegment an Record that describe the Class. This record contains the VMT = Virtual Method Table, the DMT = Dynamical Method Table, the Interfacetable of the supported Interfaces of the class, some classmember like a pointers or datas for the ParentClass, ClassName,  Instancesize, Properties and published methods, and to the TypeInfo for the Class. This TypeInfo IS the RTTI = Run Time Type Information to every Type that we use. After all the Compiler generates a big Tree of Classinformations linked to the second big Tree of Typeinformations. Now, on destruction of any Instance we can easily get all needed Information to clear any Instance-Fields that pointed to Interfaces or referencecounted Types like Strings, dynm. Arrays, Variants and other this.

You should take a look, suppose You can read assembler, into System.pas and study such procedures as .FreeInstance or _FinalizeRecord;

Hagen
0
 
Hagen040798Commented:
TObject.Free calls internal TObject.Destroy; and .Destroy is virtual. A destructor calls .FreeInstance; and this Method use some RTTI member to cleanup the Instance, they Interfaces, reference counted Fields, like Strings, dyn. Arrays, and finally calls Freemem(Self, Self.InstanceSize) to free the Instance it self.
0
 
robert_marquardtCommented:
and Self.InstanceSize is ignored because the size of the allocated block is stored inside the allocated block.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
Hagen040798Commented:
Yes, if we assume as underlaying Memorymanager the Borland Standard one.
0
 
kogerAuthor Commented:
Could you describe a little more.
Free is called to TComponent's, but there is no string propery in TComponent. How does TComponent know how to clear the property and free it?
0
 
kogerAuthor Commented:
Now that's an impressive answer :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.