I have an ActiveX exe with Thread per object set so each object will
reside in it's own thread.
Now, when creating the objects I can see the thread count of the
process increase and when they are destroyed I can see the thread count
decrease and reach it's starting point after all objects were
destroyed. How ever the memory that the process use remain high much
more then it's initial value.
Since I thought this is a memory leak in my code, I looked for a
possible error that will cause this, but could not found one.
So I went and wrote an ActiveX exe - with Thread per object option -
that expose one object type that does nothing with no properties and no
data members simply an empty object.
I started a few of that object and as before I could see the thread
count increase and decrease as objects were created/destroyed but again
the memory used by the process did not decrease to it's initial value
after all objects were destroyed. It stays much higher - for example
init value 5000K, after 1000 objects were created/destroyed - 20000K.
This scenario - to my knowledge - rule out the possibility of memory
leaks.
Can someone tell me if it is normal, and why this happens?
Tony Proctor
"Ophir" <oph...@netvision.net.il> wrote in message
news:1107779376....@l41g2000cwc.googlegroups.com...
Run your test a few times and see how the 'Mem Usage, 'Page Faults', and 'VM
Size' over a longer period of time.
Tony Proctor
"Ophir" <oph...@netvision.net.il> wrote in message
news:1107955127.9...@o13g2000cwo.googlegroups.com...
Tony Proctor
"Ophir" <oph...@netvision.net.il> wrote in message
news:1108062102.1...@c13g2000cwb.googlegroups.com...