Filetransfer stuck and freeze

[AnotherUVNCuser]

Wow, i didn't expect to see that many new messages from you

The problem exists if you watch a video (for screen update) on remote computer and answer in chat.
Maybe the screen update and the chat messages are mixed.

Hmm, i only showed the chat window to demonstrate the server was an UltraVNC server and no other VNC server program

I was extracting all network code parts in a lib as part of a viewer rewrite.
Perhpas i find the bug while on that.

Do you use Wireshark for that? (useful/powerful free network traffic inspection program)

Does stopping a filetransfer work on your end?


Good luck figuring it all out (may the code be with you )

[AnotherUVNCuser]

Well, the viewer somehow still manages to crash fairly often, but i don't know why or by what the crash is caused.

I can only say that it happens when there are multiple connections/sessions active.
When not interacting with the remote computers, the viewer eventually crashes.

(tested with 1.2.1.6 x86/x64 under Windows 10 x64)

[Rudi De Vos]

crash or disconnect ?
Can you pm the ini file ( just erase the passwd)

[AnotherUVNCuser]

crash or disconnect ?
Can you pm the ini file ( just erase the passwd)

I'm sorry, i noticed that i was using the the wrong vncviewer .exe (standard 1.2.1.6 instead of the 1.2.1.6 with tightVNC/jpeg fix)...



off-topic: When opening [Network Favorites] i often see a target.lnk and desktop.ini file, but no actual network files/folders (when downloading and opening target.lnk i see a \\network location)

Isn't it possible to browse/navigate through network shares and download the shared files using the Filetransfer manager?

[AnotherUVNCuser]

Well Rudi, apparently the crashing does occur with the "fixed" (24 sept 2017 22:02:19) 1.2.1.6 build, as well...

The viewer isn't closing/disconnecting either, because i didn't touch the viewer nor the remotely connected computers when the crash occurred.

(i've tested it with multiple/simultaneous remote connections to different computers, and left them alone/idle for a while).


I'm not sure how useful my .ini would be, but i'll pm it you regardless.

[Rudi De Vos]

Found something

The viewer send keepalives to the server.

When you have a static screen ( tested with hyperv and just do nothing), the keepalive prevent
-switches to close the line
-server recv timeouts

But the viewer still can timeout. Sending something doesn't reset the recv timeout.

A solution would be
viewer send keeaplive
server answer with his own keealive
So both recv sockets are reset

Doing some tests to check if this doesn't break other things

[AnotherUVNCuser]

Found something

The viewer send keepalives to the server.

When you have a static screen ( tested with hyperv and just do nothing), the keepalive prevent
-switches to close the line
-server recv timeouts

But the viewer still can timeout. Sending something doesn't reset the recv timeout.

A solution would be
viewer send keeaplive
server answer with his own keealive
So both recv sockets are reset

Doing some tests to check if this doesn't break other things

I really appreciate the effort Rudi. If i was able to develop and commit fixes myself, i would gladly contribute them.

Hopefully you can solve this particular problem because its a very common thing to sometimes work on simultaneous connected remote systems

edit: I noticed the topic with the timeout fixed build. Gonna do some testing now. Thanks!

Best regards,
AnotherUVNCuser

[CPS]

Hi Rudi, thanks for all your hard work all these years.

I found a small bug on the newly created Force Close button, if you resize the transfert window, it stays in place.

[Prisma]

Also thanks for all your hard work and dedication all these years, Rudi.

Waiting for the fix. Give us a hint, when there is something to test. Sounds like both winvnc.exe and vncviewer.exe have to be changed?


(Offtopic: Have you seen this https://github.com/Microsoft/winfile ?
Probably something for a complete new filetransfer GUI. You talked/thought about that a view years/moths/don't-know ago.
Feasible as 2 winfile windows fixed side by side. But you would have to try to implant a file-object handler for remote files/folders. Don't know if that's possible.)