On Fri, 25 May 2001, Mac Reiter wrote:
> Now, if the suspected problem is one of event frequency and the system not
> having time to process events and free them, then a 10% CPU usage would
> disprove that hypothesis. If the suspected problem is one of Resource
> leakage, then a powerful machine would actually tend to crash sooner --
> more processing power means you can perform the resource leaking code more
> times per second, which means you leak faster...
> Anyway, my primary purpose was to clarify "Resources". Microsoft's
> unfortunate choice of term has caused confusion ever since Windows 3.0 (and
> probably before that).
:) I think the problem is that Windows has a relatively small
window-message queue size. Messages get queued for the WinVNC process to
indicate display state changes but if WinVNC is attempting to send an
update, these messages are not read and the system can lock up. I've been
trying to work out a neat way to fix this but the way in which window
handles are managed makes it extremely difficult.
Cheers,
James "Wez" Weatherall
--
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 [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
