Celebrating the 22th anniversary of the UltraVNC: https://forum.uvnc.com/viewtopic.php?t=38031
Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864

Development: UltraVNC 1.5.0.X: https://forum.uvnc.com/viewtopic.php?t=38037

Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Search found 5 matches

by Jikaro
2014-09-16 09:15
Forum: Olders
Topic: Zombie process
Replies: 7
Views: 6429

Re: Zombie process

This appears to have corrected the problem. I can create the bug in the release version, then close that process and use either of the test versions in the same situation and they both close the process correctly.

Thanks!
by Jikaro
2014-09-10 02:35
Forum: Olders
Topic: Zombie process
Replies: 7
Views: 6429

Re: Zombie process

Thanks. I'll take a look.
by Jikaro
2014-09-04 11:50
Forum: Olders
Topic: Zombie process
Replies: 7
Views: 6429

Re: Zombie process

Okay, I tried the x64 version, but the problem persists. The process does not close correctly under certain conditions. The difference in this case was that trying to start a new process caused a dialog box to appear which said that UVNC was sill running. The x86 version is generating the same ...
by Jikaro
2014-09-03 03:53
Forum: Olders
Topic: Zombie process
Replies: 7
Views: 6429

Re: Zombie process

I'll check it out. Thank you.
by Jikaro
2014-09-02 04:33
Forum: Olders
Topic: Zombie process
Replies: 7
Views: 6429

Zombie process

Recently I noticed that under certain conditions, UVNC will not allow me to log back in after closing the server remotely and then restarting it (via a daemon). I tried upgrading to the most recent version (1.2.0.1) but the problem persisted. Upon investigation, I found that when this occurs, there ...