1.2.1.7 viewer crashing when minimized

[andrewk89]

Running UltraVNC Viewer 1.2.1.7 on Windows 7 x64. After minimizing the viewer window, the viewer crashes after a few minutes. every time.

Server is Windows 10 x64 running the same version.

Viewer options are

• Hextile
• Full Colors
• Auto size / 90% scaling

Forget which version I was running before upgrading. Either 1.2.1.6 or 1.2.1.2 on both client and server. Using the same settings, neither viewer had this issue.

Here's what I pulled out of the Event Viewer

Code: Select all

Faulting application name: vncviewer.exe, version: 1.2.1.7, time stamp: 0x5a57b793
Faulting module name: vncviewer.exe, version: 1.2.1.7, time stamp: 0x5a57b793
Exception code: 0xc0000005
Fault offset: 0x000000000007f30d
Faulting process id: 0x1d48c
Faulting application start time: 0x01d3a07a9606d92c
Faulting application path: C:\Misc\Software\vncviewer.exe
Faulting module path: C:\Misc\Software\vncviewer.exe
Report Id: 4a038f2c-0c70-11e8-8de8-34e6d73ce7fe

[Rudi De Vos]

Anyone else can repeat this issue.

Viewer crash after been minimized for a while ?

[TeddyN]

Anyone else can repeat this issue.
Viewer crash after been minimized for a while ?

Yes. I had reported this under 1.2.1.7 thread several days ago. I have 4 PCs with Win 7 Pro 64, and installed UVNC using exe-installer to them. I had no problem with 1.2.1.6.

With 1.2.1.7, when the remote window is minimized, UVNC crashes on Viewer side. My impression is that the remote window also crashes when it is not minimized but inactive, but I'm not sure.

When Server side is 1.2.1.6 but Viewer is 1.2.1.7, Viewer doesn't crash but sometimes the connection is lost thouth it can be reconnected.

Hope my info helps.

[Rudi De Vos]

Let's see if i can repeat it in debug mode ..

[ferngesteuert]

I can also reproduce issue.
Host/Server is windows 10 and Viewer runs on windows 7.

Reproduced with:
1) Start connection and switch to full screen
2) restore window (top bar)
3) minimize viewer and wait a few minutes

It viewer is minimized and restored within seconds it works, but as soon as it minimized for a while it crashes on restore window.

Hope a fix can be provided.

regards, Michael

[andrewk89]

Update: I switched to the 1.2.1.5 viewer on Windows 7 x64. Server is still 1.2.1.7 on Windows 10 running as a service.

Within a minute or two after minimizing, the 1.2.1.5 viewer also crashes.

[Phil]

Hello,

I encounter exactly the same difficulties.
Server W7-32 v1.2.1.7
Viewer W10-64 v1.2.1.7
vncviewer crash after a few minutes.

Source : Application Error
Id : 1000

Nom de l’application défaillante vncviewer.exe, version : 1.2.1.7, horodatage : 0x5a57b793
Nom du module défaillant : vncviewer.exe, version : 1.2.1.7, horodatage : 0x5a57b793
Code d’exception : 0xc0000005
Décalage d’erreur : 0x000000000007f30d
ID du processus défaillant : 0x2544
Heure de début de l’application défaillante : 0x01d3c0ea250e996b
Chemin d’accès de l’application défaillante : C:\Program Files\UltraVnc\vncviewer.exe
Chemin d’accès du module défaillant: C:\Program Files\UltraVnc\vncviewer.exe

I installed v1.2.1.7 because with v1.2.1.6 I had regular disconnections (not crashes), followed by automatic reconnection :

Server W7-32 v1.2.1.6
Viewer W10-64 v1.2.1.6

If that can help you find the solution ....

Thank you very much.

[TheRogue]

Hello, I was running VNC Server 64 v1.2.1.2 on a desktop running Windows 10 64bit, and using VNC 64 Viewer v1.2.1.2 on my Laptop running Windows 10 64bit and the viewer kept crashing when minimized. This began about 2 weeks ago, early May. Before that I had not had this issue. I found the latest version was 1.2.1.7 so I uninstalled both server and viewer, and reinstalled the latest version on each computer. The crashing continues, repeatable 100%, any time I minimize the viewer on my laptop, it crashes when I try to bring it back up. I had hoped the new version would remove the problem, but I can see that I am not alone in having this issue.

[AnotherUVNCuser]

I found the latest version was 1.2.1.7 so I uninstalled both server and viewer, and reinstalled the latest version on each computer. The crashing continues.

Perhaps you can try the updated but unfinished 1.2.2.x release @ http://forum.ultravnc.info/viewtopic.ph ... 60#p103731

[TheRogue]

Perhaps you can try the updated but unfinished 1.2.2.x release @ http://forum.ultravnc.info/viewtopic.ph ... 60#p103731

I went to that topic, I read some posts about 1.2.2.0 still having crash issues, but a new 1.2.2.1 did not, so I grabbed 1.2.2.1 and put them 4 files in it inside my client machine, it still crashed when I minimized the program.

[Rudi De Vos]

i can't repeat it...

Does it also crash when you keep the viewer open and don't do anything in the window.
Does the server has some screensaver active?

[TheRogue]

I also went in and updated the server files to 1.2.2.1 and for about 5 minutes right now the client has been minimized and has not crashed. Before it would crash 10-20 seconds after I minimized it. So it looks like updating both server and clients may have the issue resolved.

[gneuner]

i can't repeat it...

Does it also crash when you keep the viewer open and don't do anything in the window.
Does the server has some screensaver active?

My vncviewer 1.2.1.7 on a 64-bit host crashes frequently. It happens after a minute or so regardless of being minimized. It's all but unusable connecting to a 64-bit server - it seems more stable with a 32-bit server for whatever reason.

Another annoyance: vncviewer 1.2.1.7 seems always to auto select "best settings", completely ignoring the settings file for the connection. I've tried recreating the files from 1.2.1.7, but it makes no difference. I can change the settings after connection, but the initial connection is always wrong.

George

[Rudi De Vos]

Meantime 1.2.2.1 has been pre-release
https://forum.ultravnc.net/viewtopic.php?f=72&t=33894

All bug fixed need to be done on the latest code, can you check if the issue still exist in this version

[gneuner]

Meantime 1.2.2.1 has been pre-release

I downloaded the 1.2.2.1 pre-release. I have only looked at the viewer so far, but it still does not respect saved connection settings [even ones it saved itself]. It auto selects "best settings" every time.

On a 64-bit client the viewer crashes immediately on connecting to a 64-bit 1.2.1.7 server if I change the connection settings before trying to connect.

When I let it connect with "best settings", it runs OK for 10-20 minutes, surviving being minimized for a time and then opened again ... but then it crashes - sometimes while minimized, sometimes while open.

I will try it against the 1.2.2.1 server and see what happens.
George

[gneuner]

Update:

I tried 1.2.2.1 using both 64-bit viewer and 64-bit server. The viewer appears stable when used with its own server. It still crashes when connected to a 1.2.1.7 server.

However, the 1.2.2.1 server does not seem to work on Win7 unless a user is logged in. I did install it as a service and the service is configured to start automatically. But no connection can be made when all users are logged out.

I know this is pre-release, but it has got to work without a user logged in.

George

[Rudi De Vos]

The crash was caused by the keepalive messages sended by the server.
Server update needed, viewer crash caused by server message...

I don't see why it should not work as service on win7... natural it should work.

The whole idea behind a prerelease is finding bugs...i spend all time on programming and don't have the proper time to test it on
all platforms and different networks.

[gneuner]

The crash was caused by the keepalive messages sended by the server.
Server update needed, viewer crash caused by server message...

Not sure I understand - hasn't keepalive been in UVNC for a while? 1.2.1.2 has settings for it. And isn't keepalive a standard mechanism? Repeat the last ACK'd TCP packet number?

I don't see why it should not work as service on win7... natural it should work.
The whole idea behind a prerelease is finding bugs...i spend all time on programming and don't have the proper time to test it on all platforms and different networks.

I'm not faulting you (or anyone else) ... I appreciate your effort. I'm not sure why it doesn't work without a user logged in. Maybe somebody can figure that out. For the time being, I'm reverting to 1.2.1.2 (which I know works ).

George

[Rudi De Vos]

Just tested the 1.2.2.1on a server 2008R2 this should more or less act as win7
That seems to work and i can connect running uvnc as service. ( after some firewall issue's)
Using the default ini

Keepalive is actual a vnc msg, it has nothing todo with the tcp packet.
Like sending a mouse or keyboard msg.
My fault was that is run a seperate thread and it need to be syncronized with the other messages.

The message was added a time ago to be able to send messages between
server<->repeater and keep the line open.

Gonna install a win7 on a VM to check again.

[gneuner]

Just tested the 1.2.2.1 on a server 2008R2 this should more or less act as win7
That seems to work and i can connect running uvnc as service. ( after some firewall issue's)
Using the default ini

Yes, 2008RC2 should be the same as Win7. Firewall hmm? I'll have to look at that. Offhand I can't think of a reason the firewall would block it only when no user is logged in.

Keepalive is actual a vnc msg, it has nothing to do with the tcp packet.
Like sending a mouse or keyboard msg.

Ah! So it's not TCP's keepalive ... it's a custom mechanism. Now I understand the version dependency.

George

[Rudi De Vos]

Retested with win7 using the 64bit exe this time.
Used the setup exe download

installed, disabled firewall , set a passwd
rebooted win7
Connected the viewer to the logon screen
logged on

Can't repeat it on my win7

[gneuner]

installed, disabled firewall , set a passwd
rebooted win7
Connected the viewer to the logon screen
logged on

But does it work with the firewall on? Can't very well turn off protection.

George

[Rudi De Vos]

If i add exceptions for winvnc i can turn it back on.

For fast testing i always temp disable it. When it works without, you know it's a firewall settings.
Some Firewalls use ports, other allow exe and use a checksum.. a new exe even on the same spot need
to be allowed again.

But in both cases it should work as application AND service or not at all.

Usual i run it once as application. If something popup like ... port already in use or please allow firewall.
You can't see it when winvnc is running as servcie... messages goes on the invisable service screen.

When running as service, make sure the service reffer to the correct exe.
If you installed winvnc on spot A as service and later install another version it in folder B
The service still reffer to spot A.
remove service/ install service via systray running as application.

If auto port is selected and port 5900 is in use it use port 5901....

[alexanderl044]

Hello all, I'm only installed this product and meet given problem now. So, somebody know how fix this? I'm cannot disable firewall.
Please help. Thanks!

[Rudi De Vos]

Latest version is 1221.
Should be fixed in that version.