logo

The ConnectWise Control forum has moved to ConnectWise University! This forum has been locked and is in read-only mode. Click here for instructions on how to access the new forum.

Welcome Guest! You can not login or register.

Notification

Icon
Error

Options
Go to last post Go to first unread
rgreen83  
#1 Posted : Monday, October 12, 2015 1:37:27 PM(UTC)
rgreen83


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 2/16/2015(UTC)
Posts: 69
United States
Location: Missouri

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
We have noticed that when we connect to sessions on 2003/xp machines the CPU goes to 100% on the ScreenConnect.WindowsClient.exe process. Only happens when a host session is connected, and all of the ones we have tested are access sessions.

Scott  
#2 Posted : Monday, October 12, 2015 2:03:34 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
What kind of video drivers are in use on these remote machines? Are they Matrox drivers?

Also, does the CPU usage get any better if you blank the Guest's monitor and wait ~30ish seconds?
ScreenConnect Team
rgreen83  
#3 Posted : Monday, October 12, 2015 2:35:12 PM(UTC)
rgreen83


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 2/16/2015(UTC)
Posts: 69
United States
Location: Missouri

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
All the ones I have looked at are VMs so they have the vmware tools svga driver like they have always had and have had SC on them since 5.0 without this issue, and any that had matrox or other driver issues in the past we have already corrected those.

Blanking the guest monitor appears to have no effect.

I have installed each 5.5 build so far and we did not notice this issue with the previous builds to 9749.

Thanks for the quick response!
Scott  
#4 Posted : Wednesday, October 14, 2015 1:53:33 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
I just registered this internally and I am registering it as a defect. I don't have an exact ETA on when the development team will find a fix, but it's obviously a very high priority issue so it should be sooner rather than later.

Thanks for reporting!
ScreenConnect Team
rgreen83  
#5 Posted : Thursday, October 15, 2015 5:45:07 PM(UTC)
rgreen83


Rank: Advanced Member

Medals: Level 1: Random Act of Kindness! Received One Thanks!

Joined: 2/16/2015(UTC)
Posts: 69
United States
Location: Missouri

Thanks: 6 times
Was thanked: 3 time(s) in 3 post(s)
I have tested 5.5.9788.5765 and can confirm this issue is now fixed.
rmmccann  
#6 Posted : Thursday, October 15, 2015 6:59:54 PM(UTC)
rmmccann


Rank: Advanced Member

Medals: Level 2: Lent a Helping Hand! 10 Thanks!

Joined: 12/16/2012(UTC)
Posts: 184
Location: MN, USA

Thanks: 17 times
Was thanked: 21 time(s) in 18 post(s)
Is this unique to 5.5.x or is it also present in 5.4.x? I'm waiting for the next 5.4 stable to upgrade and don't want to be caught with any nasty bugs such as this.
Scott  
#7 Posted : Thursday, October 15, 2015 7:20:41 PM(UTC)
Scott


Rank: Administration

Medals: Level 4: Wise Old Owl! Received 100 Thanks!

Joined: 3/28/2014(UTC)
Posts: 2,862
United States

Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
I have not seen any report of this behavior affecting 5.4 installations.
ScreenConnect Team
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.