Using TightVNC Server for Windows - Version 2.8.85 (built on Jun 17 2024 ar 15:05:18)
with active client connections (same TightVNC version):
Number of CPU threads increases dramatically (e.g. monitored by Windows resource monitor, see attached screenshots) when server engages 'screen off' (power saving settings), while VNC client connection is active (e.g. from 24 to 18.500 CPU threads within about one hour screen off). Ultimately leads to extreme memory consumption and system slowdown/instability.
Does not occur when VNC client connection is inactive.
Behavior not observed for Windows 10 Pro yet.
