Had a couple of Server (Ubuntu LTS 14 Screen Connect 6.6.18120.6697) Crashes and Reboots today coincidentally just after initiating a large Folder Copy during an Access Host Session.
We normally find Screen Connect extremely stable - and would have ignored it, but it happened twice whilst performing similar actions on the same Access Client.
Today we were assisting an Access Client (Windows 10 Pro) to copy from one USB external HDD to another USB external HDD. The first copy was attempting to copy a folder containing approx 240,000 files and totaling approx 240GB. Using Windows Explorer we Copied then Pasted, and then the Access session froze. Freezing is not that uncommon (as we run from a slow ADSL based site) - so our initial reaction was to wait. We then noticed that the ScreenConnect Service had crashed on our Server and was attempting to restart. Checking RAM, CPU and FreeDisk seemed all ok. We probably didnt help the situation as we became impatient and restarted the entire Ubuntu virtual server.
Once the Server restarted, other Access Clients reconnected and we could establish a Host Session with them easily. However attempting to re-establish a Host Session with the initial Client crashed the Server again.
We restarted again - and left the originating problematic Client alone for approx 2 hours (as it was busy copying the data anyway).
We returned later (although had used Screen Connect extensively connecting to other clients during this period)... all ok.
We then attempted to copy another folder, this time with approx 50GB and again 1000's of files and the Server crashed again almost immediately.
We left everything alone again - and let the copy complete.
Our suspicion is that Screen Connect is attempting to copy the files up to the Host Clipboard - or potentially waiting for the Guest to determine the overall file size (perhaps before it chooses to copy to the host or not), and the Guest itself is taking minutes or longer to respond as its still calculating the overall size of the folder (files) that its copying.
We wouldnt normally raise a bug request without researching the issue further - but thought we might bring this coincidental Server crash to your attention as you might already be aware of it and therefore we can leave this as a known issue or you might want our help attempting to further diagnose the potential cause and could offer advice on where to look further for the potential cause.
Customer support service by UserEcho