Finalizer Queue

[ajbecker]

Thanks for all your help. Unfortunatly, it looks like the problem is
elsewhere. After adding the following code into the main loop of the
unmanaged code, the memory bloat still occurs.

{
HANDLE hThread = GetCurrentThread();
// Spin the message loop.
MsgWaitForMultipleObjects(1, &hThread, TRUE, 100, 0xFFFFFFFF);
}

Again, thanks for your help, but it looks like it's back to the drawing
board for me.

 

[Willy Denoyette [MVP]]

| Thanks for all your help. Unfortunatly, it looks like the problem is
| elsewhere. After adding the following code into the main loop of the
| unmanaged code, the memory bloat still occurs.
|
| {
| HANDLE hThread = GetCurrentThread();
| // Spin the message loop.
| MsgWaitForMultipleObjects(1, &hThread, TRUE, 100, 0xFFFFFFFF);
| }
|
| Again, thanks for your help, but it looks like it's back to the drawing
| board for me.
|

Note that this is not enough to spin a message loop, this only picks up a
single message from the COM created invisible window queue.
But I suggest you try to find out if the finalizer is really blocked, this
can be achieved by attaching a native debugger like windbg.exe (part of the
downloadable "debugging tools for windows") and SOS.dll (part of the
framework).

Willy.