Hi,
How is this possible that destructor is not called
when I quit my application? This is toolbar for IE.
For one of my classes destructor is not called causing
memory leaks. Class was created on the stack and there is no inheritance.
thanks for advice

write part of the source code. which is the class and where it is used.


andrew wrote:
> Hi,
> How is this possible that destructor is not called
> when I quit my application? This is toolbar for IE.
> For one of my classes destructor is not called causing
> memory leaks. Class was created on the stack and there is no
inheritance.
> thanks for advice

I am assuming you are doing this thru COM. Depending upon your flow,
its possible that there is a reference to it by some other object (IE
or your own code). That may cause your module to stay in memory. There
is no general way to figure it out. Can  you see what is ref count on
the object when you expect it to be destoryed?

---------
Ajay Kalra
ajaykalra@yahoo.com

yes, this is com plug in for IE.
Probably you're right -something sitting in memory after close.

"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message 
news:1113584702.968664.309990@f14g2000cwb.googlegroups.com...
>I am assuming you are doing this thru COM. Depending upon your flow,
> its possible that there is a reference to it by some other object (IE
> or your own code). That may cause your module to stay in memory. There
> is no general way to figure it out. Can  you see what is ref count on
> the object when you expect it to be destoryed?
>
> ---------
> Ajay Kalra
> ajaykalra@yahoo.com
>