Memory leak issue, memory management of unmanaged code

[logicaldna]

hi i'm having a issue with memory management in a COM which uses MSXML (cause of memory leak) if i use a c# wrapper around the COM which is then called from .net webservice will CLR take care of memory management for me( essentially Garbage collection) if not by design can i force GC to take care of memory leaks in COM this is very urgent, please help ! :(( sorry i'm posting it in different forums at a time but hope you will see a desparation :->

Chase your dreams ! http://eminencetech.net[^]

[Shy Agam]

The GC does not re-claim unmanaged memory. Regards, Shy.

[logicaldna]

thanks for the reply, but can i force it in anyway, is it possible if i use COM as RCW

Chase your dreams ! http://eminencetech.net[^]

[Shy Agam]

You cannot force the GC to collect objects from unmanaged memory. The GC works only on objects created by the CLR. Hence the expression "UNMANAGED memory". :) If your COM object contains cleanup methods, use them.

logicaldna wrote:

is it possible if i use COM as RCW

Sorry, but I don't think I know what RCW means... Maybe someone else here can help you with that.

[logicaldna]

shyagam wrote:

If your COM object contains cleanup methods, use them

i have tried all and even COuninitialize is not cleaning the memory dam this MSXML:confused: thanks anyways sagar

Chase your dreams ! http://eminencetech.net[^]

[Jimmanuel]

When using COM objects in C# setting an object to null isn't all that's required to signal it ready for Garbage Collection. First a call must be made to Marshal.ReleaseComObject(aComObjectVariable) to decrement it's reference counter in the RCW. MSDN[^]

[Paul Conrad]

logicaldna wrote:

i'm posting it in different forums at a time

That's not polite and it gets people ticked off and less likely to respond.

---

"You will see a delete button on each of your posts. Press it." - Colin Angus Mackay