NT4 handle leak

[James "Wez" Weatherall]

> Handle- and memory leaks have already been reported earlier, but I did not
> found any answer or solution.
>
> I am using WinVNC 3.3.3R2 on NT4 and found the following behaviour:
>
> WinVNC ist starting with 43 handles.
> After the FIRST client session WinVNC has 4 more handles (2 desktop / 2
> file)
> After the SECOND session WinVNC occupies another 3 handles, (2 desktop / 1
> file)
> Every further session increase the handle count by 2 (2 desktop)

Christian Senn posted this query about leaks in WinVNC under NT4 near the
beginning of February.  I've looked into it and it transpires that the
problem is in two threads which switch into the current desktop at all
times.  If they are still in a desktop other than their original one when
they quit, the new desktop's handle is never freed, hence the leak.
Unfortunately, even if I place some code which switches those threads back
into their original desktop before destroying the threads, Windows NT won't
let me free the handles.

I've read and re-read the APIs for this set of desktop management calls and
I cannot find a way around this - it just isn't behaving as documented, as
far as I can tell.

If anyone on the list has used desktops extensively before under NT and has
some idea what might be wrong, please let me know...

Cheers,

James "Wez" Weatherall
--
          "Xenophobes should go back to Xenophobia"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK                              - Tel : 343000




---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------