.net visual c++ 2003 gcroot cleanup/memory leak question

[rabidus]

> class UnmanagedClass
> {
> public:
> gcroot<System:: Xml::XmlDocumen t *>pMc;
>
> UnmanagedClass( System::Xml::Xm lDocument * in)
> {
> pMc = in;
> }
>
> ~ UnmanagedClass( )
> {
> delete pMc;
> }

When I try to compile this code, I get the error:

\x.cpp(92): error C3841: illegal delete expression: managed type 'System::Xml::X mlDocument' does not have a destructor defined

If I remove the delete pMc from the destructor, the code compiles, however memory is leaked if I create a new unmanaged object, (from an unmanaged class) and then delete the unmanaged object. I have tried calling garbage collect from managed code after I have created an deleted the unmanaged object, and there is still a lot of memory that does not get freed. Does anyone have any ideas on why I'm getting the error? Or maybe have an idea for a workaround?

Thanks for your time!!

[RedSon]

> class UnmanagedClass
> {
> public:
> gcroot<System:: Xml::XmlDocumen t *>pMc;
>
> UnmanagedClass( System::Xml::Xm lDocument * in)
> {
> pMc = in;
> }
>
> ~ UnmanagedClass( )
> {
> delete pMc;
> }

When I try to compile this code, I get the error:

\x.cpp(92): error C3841: illegal delete expression: managed type 'System::Xml::X mlDocument' does not have a destructor defined

If I remove the delete pMc from the destructor, the code compiles, however memory is leaked if I create a new unmanaged object, (from an unmanaged class) and then delete the unmanaged object. I have tried calling garbage collect from managed code after I have created an deleted the unmanaged object, and there is still a lot of memory that does not get freed. Does anyone have any ideas on why I'm getting the error? Or maybe have an idea for a workaround?

Thanks for your time!!

I'm a little confused. Presumably when you are creating a pointer to an object some other bit of code is going to do the creation of that object and then pass it to your application. So if someone else is doing the creation why are you doing the deletion? Other then that I have no idea how to destroy an XmlDocument object. The help on MSDN is not very useful, except to perhaps say use the removeAll method and then set your pointer to null. That way if nothing is pointing to that object anymore the GC should then take care of it. The problem is GC may take a little while to get to it.

[rabidus]

I'm a little confused. Presumably when you are creating a pointer to an object some other bit of code is going to do the creation of that object and then pass it to your application. So if someone else is doing the creation why are you doing the deletion? Other then that I have no idea how to destroy an XmlDocument object. The help on MSDN is not very useful, except to perhaps say use the removeAll method and then set your pointer to null. That way if nothing is pointing to that object anymore the GC should then take care of it. The problem is GC may take a little while to get to it.

What I'm trying to do is to delete the pointer so that reference to the object goes away. Garbage collection isn't picking up the object, so I'm trying to find out why.