Erik Collett

Not crashing, but freezing. Specifically with WebEx running

7 posts in this topic

I have two systems, a work computers and a personal computed, that I'm unifying with Synergy.

 

With the recent bump to 1.8.5, I haven't had any issues... until I run WebEx on my "slave" machine.

 

This may have something to do with control of the mouse trying to be "grabbed" by WebEx if you are trying to control the remote computer. However, I haven't had a problem with this on the 1.8.4 version and before. Now, if my cursor touches an active WebEx, it freezes the entire machine for a moment, and then replays the buffer (of me madly trying to find the cursor again).

 

It will work for another 20 to 30 seconds, then freeze again for around 6 seconds. The freeze and working seems random, so it's hard to predict. If I just use my work computer's trackpad, I'll work just fine.

 

It's very specific to WebEx, though. Hopefully, it is easy to reproduce... and not just my machine.

Share this post


Link to post
Share on other sites

I am having this same issue - but I don't remember if it happened on previous builds, but I know it has happened for at least a few months. I can run Webex on either machine (host or client,) and the issue happens, followed by a "spike" of synergyc process cpu usage where it jumps up to ~15% for a second, then back to normal levels.

 

Both machines are Windows 10, build 1.8.5-stable-a18eba7.

 

I just isolated this to Synergy today, so I'm going to downgrade to test.

Share this post


Link to post
Share on other sites

Hi, i've a XP Server and a WIN10 laptop client, and every random minutes from 2 or 3 to 20 or 30 minutes the mouse and key frezees on the client, the client goes dead on synergy server and after a few seconds or 1-2 minutes it goes live again.

contacted support and found out to be a Bug, they take note of it and will adress it on a later version.

until now y was using win7 laptop client, and was working smoothly, so it has something to do with win10.

Share this post


Link to post
Share on other sites

I've started experiencing this issue after upgrading to 1.8.7

Was there any mention of a fix in any previous release? Considering downgrading to 1.8.4, did this work for anyone?

Share this post


Link to post
Share on other sites
I've started experiencing this issue after upgrading to 1.8.7

Was there any mention of a fix in any previous release? Considering downgrading to 1.8.4, did this work for anyone?

 

I tried going back to a 1.7 something a while back with no luck, but I haven't tried 1.8.4, but from what I remember, it was still happening then too.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now