SacredKow

Lag - Can we identify common denominators?

31 posts in this topic

Hello All,

I have been struggling with consistent lag on my client machine. I am trying to identify why it happens. Perhaps others that have this problem can chime in and we can identify what is happening. This has been issue but no real answers so far.

My environment:
Windows 10 Desktop (older machine) - Wired ethernet connection
Windows 10 laptop (newer machine) - Wireless only

These machines used to work just fine, few hiccups here and there, but generally worked great on 1.x and even early 2.x.

In the last month or so it has drastically deteriorated whereby the majority of the time it is unusable.

Unusable means:

 - Mouse and often the keyboard on client machine is incredibly laggy
 - Moving mouse pauses then jumps - closing a window or selecting anything is impossible
 - At times I will be typing and the connection appears to reset and is thrown back to the server machine (desktop)
 - At times I have to reset the service to in order to connect back to the client screen - trying to move mouse to client resembles head banging on brick wall (this just happened right now)
 - I tried dropping back to 1.x, oddly enough that seems to be no better when it used to be great
 - I am now trying 2.0.7 - absolutely no difference

I have a brand new mesh router, I sit 10 feet from it, wifi signal shouldn't be the issue.
I run Kaspersky - but I have totally disabled it and see no positive impact.

What other questions aren't being analyzed?

 

Share this post


Link to post
Share on other sites

Apologies, perhaps this should be moved under 2.x, thought I was in that forum.

Share this post


Link to post
Share on other sites

Moved and approved. Nice job of reporting and troubleshooting.

  • Like 1

Share this post


Link to post
Share on other sites

I've had the same mouse effect on occasion. To me, it feels like a runaway background process, but I haven't been able to pinpoint one.

Have you updated to 2.07 yet? If you haven't installed it yet, try doing a clean install. Use Windows uninstall to remove the old Synergy from both before installing the new version.

Share this post


Link to post
Share on other sites


My environment:
Windows 10 Desktop  - Wired ethernet connection
Macbook Pro laptop  - Wireless only (5g)

Version: 2.0.7


Seeing lots of lag myself, as well as a constant disconnect / reconnect from my mac.

[ Core    ] [2018-03-13T13:42:21] DEBUG: dropped bogus delta motion: -962,-362
[ Core    ] [2018-03-13T13:42:21] INFO: switch from "RYANWAGGONERML3" to "DESKTOP-R9QQ9R9" at 1,181
[ Core    ] [2018-03-13T13:42:21] INFO: entering screen
[ Router  ] [2018-03-13T13:42:22] debug: ClientProxy: Received client connection for RYANWAGGONERML3 from screen 120413
[ Router  ] [2018-03-13T13:42:22] debug: Error reading from core server: The I/O operation has been aborted because of either a thread exit or an application request
[ Router  ] [2018-03-13T13:42:22] debug: Terminating core server read loop
[ Core    ] [2018-03-13T13:42:22] NOTE: client "RYANWAGGONERML3" has disconnected
[ Core    ] [2018-03-13T13:42:22] DEBUG: active sides: 2
[ Core    ] [2018-03-13T13:42:22] NOTE: accepted client connection
[ Core    ] [2018-03-13T13:42:22] DEBUG: received client "RYANWAGGONERML3" info shape=-1920,0 3360x1080 at 720,450
[ Core    ] [2018-03-13T13:42:22] DEBUG: active sides: 2
[ Core    ] [2018-03-13T13:42:22] NOTE: client "RYANWAGGONERML3" has connected

 

 

No VPN, nothing really system demanding going on. Network certainly not being bogged down.

 

Share this post


Link to post
Share on other sites

Be sure you have sent logs to Support. https://symless.com/contact/customer-support    Report your experience to support. Send logs for each machine. Trouble tickets drive development.

One last idea.

Looking at the Synergy UI, mouse-grab one of the screens and move it away from the other, so they are no longer touching. Both will probably go into 'searching' mode. Then move the screen back to touching the other. 

This is just a 'quick and dirty' way to restart the core process on both computers.

Share this post


Link to post
Share on other sites

Howdy GranPa,

I have in fact installed 2.0.7 today. I did so after a full uninstall and reboot of both machines. Not much difference. It's maddening because my desk layout doesn't easily allow for multiple keyboards, etc. I'm stymied but like you, I believe there is something causing the interference so hopefully as a group (I'm assuming there are others) we can find something we all share in common that limits the scope to identify the culprit.

Thanks!

-SK

Share this post


Link to post
Share on other sites

My logs...

Client details (and both logs submitted to Synergy.

[ Router  ] [2018-03-13T15:42:01] debug: Installing routes received from node 12654
[ Router  ] [2018-03-13T15:42:01] debug:    Route 1: dest 12654, cost 0, path []
[ Router  ] [2018-03-13T15:42:01] debug:    Route 1: not installed
[ Router  ] [2018-03-13T15:42:01] debug:    Route 2: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:01] debug:    Route 2: ignored because it leads back to to me
[ Router  ] [2018-03-13T15:42:01] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:01] debug:    Route 1: dest 12654, cost 1, path [12654]
[ Core    ] [2018-03-13T15:52:21] NOTE: server is dead
[ Router  ] [2018-03-13T15:52:21] debug: Error reading from core client: End of file
[ Router  ] [2018-03-13T15:52:21] debug: Terminating core client read loop
[ Core    ] [2018-03-13T15:52:21] WARNING: failed to connect to server: server is not responding
[ Core    ] [2018-03-13T15:52:21] DEBUG: retry in 1 seconds
[ Service ] [2018-03-13T15:52:22] debug: send screen status update SCOTT-HP1310: Connected -> Connecting
[ Core    ] [2018-03-13T15:52:22] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2018-03-13T15:52:22] debug: Saying Hello to core client
[ Service ] [2018-03-13T15:52:27] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:52:27] debug: profile has not changed, no action needed
[ Core    ] [2018-03-13T15:52:31] NOTE: server is dead
[ Router  ] [2018-03-13T15:52:31] debug: Error reading from core client: End of file
[ Router  ] [2018-03-13T15:52:31] debug: Terminating core client read loop
[ Core    ] [2018-03-13T15:52:31] WARNING: failed to connect to server: server is not responding
[ Core    ] [2018-03-13T15:52:31] DEBUG: retry in 1 seconds
[ Core    ] [2018-03-13T15:52:32] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2018-03-13T15:52:33] debug: Saying Hello to core client
[ Core    ] [2018-03-13T15:52:42] NOTE: server is dead
[ Router  ] [2018-03-13T15:52:42] debug: Error reading from core client: End of file
[ Router  ] [2018-03-13T15:52:42] debug: Terminating core client read loop
[ Core    ] [2018-03-13T15:52:42] WARNING: failed to connect to server: server is not responding
[ Core    ] [2018-03-13T15:52:42] DEBUG: retry in 1 seconds
[ Core    ] [2018-03-13T15:52:43] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2018-03-13T15:52:44] debug: Saying Hello to core client
[ Core    ] [2018-03-13T15:52:44] DEBUG: desk Default window is 0x002213be
[ Core    ] [2018-03-13T15:52:44] DEBUG: switched to desk "Default"
[ Core    ] [2018-03-13T15:52:44] DEBUG: desktop is now accessible
[ Core    ] [2018-03-13T15:52:44] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:52:44] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:52:44] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:52:44] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:52:44] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:52:44] DEBUG: close clipboard
[ Service ] [2018-03-13T15:52:44] debug: send screen status update SCOTT-HP1310: Connecting -> Connected
[ Core    ] [2018-03-13T15:52:44] NOTE: connected to server
[ Service ] [2018-03-13T15:52:46] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:52:46] debug: profile has not changed, no action needed
[ Core    ] [2018-03-13T15:57:35] NOTE: server is dead
[ Router  ] [2018-03-13T15:57:35] debug: Error reading from core client: End of file
[ Router  ] [2018-03-13T15:57:35] debug: Terminating core client read loop
[ Core    ] [2018-03-13T15:57:35] WARNING: failed to connect to server: server is not responding
[ Core    ] [2018-03-13T15:57:35] DEBUG: retry in 1 seconds
[ Service ] [2018-03-13T15:57:36] debug: send screen status update SCOTT-HP1310: Connected -> Connecting
[ Core    ] [2018-03-13T15:57:36] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2018-03-13T15:57:37] debug: Saying Hello to core client
[ Service ] [2018-03-13T15:57:41] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:57:41] debug: profile has not changed, no action needed
[ Core    ] [2018-03-13T15:57:48] NOTE: server is dead
[ Router  ] [2018-03-13T15:57:48] debug: Error reading from core client: End of file
[ Router  ] [2018-03-13T15:57:48] debug: Terminating core client read loop
[ Core    ] [2018-03-13T15:57:48] WARNING: failed to connect to server: server is not responding
[ Core    ] [2018-03-13T15:57:48] DEBUG: retry in 1 seconds
[ Core    ] [2018-03-13T15:57:49] NOTE: connecting to '127.0.0.1': 127.0.0.1:24801
[ Router  ] [2018-03-13T15:57:49] debug: Saying Hello to core client
[ Core    ] [2018-03-13T15:57:49] DEBUG: desk Default window is 0x002313be
[ Core    ] [2018-03-13T15:57:49] DEBUG: switched to desk "Default"
[ Core    ] [2018-03-13T15:57:49] DEBUG: desktop is now accessible
[ Core    ] [2018-03-13T15:57:49] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:57:49] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:57:49] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:57:49] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:57:49] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:57:49] DEBUG: close clipboard
[ Service ] [2018-03-13T15:57:49] debug: send screen status update SCOTT-HP1310: Connecting -> Connected
[ Core    ] [2018-03-13T15:57:49] NOTE: connected to server
[ Service ] [2018-03-13T15:57:50] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:57:50] debug: profile has not changed, no action needed
[ Core    ] [2018-03-13T15:58:48] INFO: entering screen
[ Core    ] [2018-03-13T15:58:48] DEBUG: start receiving clipboard data
[ Core    ] [2018-03-13T15:58:48] DEBUG: receiving clipboard 0 size=261
[ Core    ] [2018-03-13T15:58:48] DEBUG: received clipboard 0 size=261
[ Core    ] [2018-03-13T15:58:48] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:58:48] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:58:48] DEBUG: add 249 bytes to clipboard format: 0
[ Core    ] [2018-03-13T15:58:48] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:58:48] INFO: clipboard was updated
[ Core    ] [2018-03-13T15:58:48] DEBUG: start receiving clipboard data
[ Core    ] [2018-03-13T15:58:48] DEBUG: receiving clipboard 1 size=261
[ Core    ] [2018-03-13T15:58:48] DEBUG: received clipboard 1 size=261
[ Core    ] [2018-03-13T15:58:48] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:58:48] DEBUG: empty clipboard
[ Core    ] [2018-03-13T15:58:48] DEBUG: add 249 bytes to clipboard format: 0
[ Core    ] [2018-03-13T15:58:48] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:58:48] INFO: clipboard was updated
[ Core    ] [2018-03-13T15:58:50] INFO: leaving screen
[ Core    ] [2018-03-13T16:01:58] INFO: entering screen
[ Core    ] [2018-03-13T16:01:58] INFO: leaving screen
[ Core    ] [2018-03-13T16:01:58] INFO: entering screen
[ Config  ] [2018-03-13T16:02:11] info: Sending log file...

Server details:

[ Router  ] [2018-03-13T15:42:04] error: Read error on connection 6: The semaphore timeout period has expired (code 121)
[ Router  ] [2018-03-13T15:42:04] debug: Connection 6 disconnected
[ Router  ] [2018-03-13T15:42:04] debug: Removing connection 6
[ Router  ] [2018-03-13T15:42:04] debug: Removing 0 route(s) broken by removal of connection 6
[ Router  ] [2018-03-13T15:42:04] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:04] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:04] debug: Adding peer at 192.168.5.107:24802
[ Router  ] [2018-03-13T15:42:04] debug: Connection 6 terminated receive loop
[ Router  ] [2018-03-13T15:42:04] error: Read error on connection 9: The semaphore timeout period has expired (code 121)
[ Router  ] [2018-03-13T15:42:04] debug: Connection 9 disconnected
[ Router  ] [2018-03-13T15:42:04] debug: Removing connection 9
[ Router  ] [2018-03-13T15:42:04] debug: Removing 0 route(s) broken by removal of connection 9
[ Router  ] [2018-03-13T15:42:04] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:04] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:04] debug: Adding peer at 192.168.5.107:24802
[ Router  ] [2018-03-13T15:42:04] debug: Connection 9 terminated receive loop
[ Router  ] [2018-03-13T15:42:05] debug: Connecting to 192.168.5.107:24802 (attempt 1/10)
[ Router  ] [2018-03-13T15:42:05] debug: Connected to 192.168.5.107:24802
[ Router  ] [2018-03-13T15:42:05] debug: Connection 11 created
[ Router  ] [2018-03-13T15:42:05] debug: Connecting to 192.168.5.107:24802 (attempt 1/10)
[ Router  ] [2018-03-13T15:42:05] debug: Connection 6 destroyed
[ Router  ] [2018-03-13T15:42:05] debug: Connection 9 destroyed
[ Router  ] [2018-03-13T15:42:06] debug: Received route advertisement from router 12652
[ Router  ] [2018-03-13T15:42:06] debug: Installing routes received from node 12652
[ Router  ] [2018-03-13T15:42:06] debug:    Route 1: dest 12652, cost 0, path []
[ Router  ] [2018-03-13T15:42:06] debug:    Route 1: not installed
[ Router  ] [2018-03-13T15:42:06] debug:    Route 2: dest 12654, cost 1, path [12654]
[ Router  ] [2018-03-13T15:42:06] debug:    Route 2: ignored because it leads back to to me
[ Router  ] [2018-03-13T15:42:06] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:06] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:06] debug: Accepted connection from router 192.168.5.107:54008
[ Router  ] [2018-03-13T15:42:06] debug: Connection 12 created
[ Router  ] [2018-03-13T15:42:07] debug: Received route advertisement from router 12652
[ Router  ] [2018-03-13T15:42:07] debug: Installing routes received from node 12652
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: dest 12652, cost 0, path []
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: not installed
[ Router  ] [2018-03-13T15:42:07] debug:    Route 2: dest 12654, cost 1, path [12654]
[ Router  ] [2018-03-13T15:42:07] debug:    Route 2: ignored because it leads back to to me
[ Router  ] [2018-03-13T15:42:07] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:07] debug: Accepted connection from router 192.168.5.107:54009
[ Router  ] [2018-03-13T15:42:07] debug: Connection 13 created
[ Router  ] [2018-03-13T15:42:07] debug: Received route advertisement from router 12652
[ Router  ] [2018-03-13T15:42:07] debug: Installing routes received from node 12652
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: dest 12652, cost 0, path []
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: not installed
[ Router  ] [2018-03-13T15:42:07] debug:    Route 2: dest 12654, cost 1, path [12654]
[ Router  ] [2018-03-13T15:42:07] debug:    Route 2: ignored because it leads back to to me
[ Router  ] [2018-03-13T15:42:07] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:07] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Router  ] [2018-03-13T15:42:09] debug: Connected to 192.168.5.107:24802
[ Router  ] [2018-03-13T15:42:09] debug: Connection 14 created
[ Router  ] [2018-03-13T15:42:09] debug: Received route advertisement from router 12652
[ Router  ] [2018-03-13T15:42:09] debug: Installing routes received from node 12652
[ Router  ] [2018-03-13T15:42:09] debug:    Route 1: dest 12652, cost 0, path []
[ Router  ] [2018-03-13T15:42:09] debug:    Route 1: not installed
[ Router  ] [2018-03-13T15:42:09] debug:    Route 2: dest 12654, cost 1, path [12654]
[ Router  ] [2018-03-13T15:42:09] debug:    Route 2: ignored because it leads back to to me
[ Router  ] [2018-03-13T15:42:09] debug: Route table contents:
[ Router  ] [2018-03-13T15:42:09] debug:    Route 1: dest 12652, cost 1, path [12652]
[ Core    ] [2018-03-13T15:52:29] NOTE: client "SCOTT-HP1310" is dead
[ Router  ] [2018-03-13T15:52:29] debug: Error reading from core server: End of file
[ Router  ] [2018-03-13T15:52:29] debug: Terminating core server read loop
[ Core    ] [2018-03-13T15:52:29] DEBUG: active sides: 4
[ Router  ] [2018-03-13T15:52:31] debug: ClientProxy: Received client connection for SCOTT-HP1310 from screen 12652
[ Core    ] [2018-03-13T15:52:31] NOTE: accepted client connection
[ Service ] [2018-03-13T15:52:34] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:52:34] debug: profile screen status changed, screenId=12652 Connected->Connecting
[ Service ] [2018-03-13T15:52:34] debug: profile changed, storing local copy
[ Router  ] [2018-03-13T15:52:41] debug: ClientProxy: Received client connection for SCOTT-HP1310 from screen 12652
[ Router  ] [2018-03-13T15:52:41] debug: Error reading from core server: The I/O operation has been aborted because of either a thread exit or an application request
[ Router  ] [2018-03-13T15:52:41] debug: Terminating core server read loop
[ Core    ] [2018-03-13T15:52:41] NOTE: client "SCOTT-HP1310" has disconnected
[ Core    ] [2018-03-13T15:52:41] NOTE: new client disconnected
[ Core    ] [2018-03-13T15:52:41] NOTE: accepted client connection
[ Core    ] [2018-03-13T15:52:42] ERROR: invalid message from client "SCOTT-HP1310": CALV
[ Router  ] [2018-03-13T15:52:42] debug: Error reading from core server: End of file
[ Router  ] [2018-03-13T15:52:42] debug: Terminating core server read loop
[ Core    ] [2018-03-13T15:52:42] NOTE: new client disconnected
[ Router  ] [2018-03-13T15:52:52] debug: ClientProxy: Received client connection for SCOTT-HP1310 from screen 12652
[ Core    ] [2018-03-13T15:52:52] NOTE: accepted client connection
[ Core    ] [2018-03-13T15:52:52] DEBUG: received client "SCOTT-HP1310" info shape=0,0 5120x1440 at -13541,32766
[ Core    ] [2018-03-13T15:52:52] DEBUG: active sides: 4
[ Core    ] [2018-03-13T15:52:52] NOTE: client "SCOTT-HP1310" has connected
[ Service ] [2018-03-13T15:52:53] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:52:53] debug: profile screen status changed, screenId=12652 Connecting->Connected
[ Service ] [2018-03-13T15:52:53] debug: profile changed, storing local copy
[ Core    ] [2018-03-13T15:57:44] NOTE: client "SCOTT-HP1310" is dead
[ Router  ] [2018-03-13T15:57:44] debug: Error reading from core server: End of file
[ Router  ] [2018-03-13T15:57:44] debug: Terminating core server read loop
[ Core    ] [2018-03-13T15:57:44] DEBUG: active sides: 4
[ Router  ] [2018-03-13T15:57:45] debug: ClientProxy: Received client connection for SCOTT-HP1310 from screen 12652
[ Core    ] [2018-03-13T15:57:45] NOTE: accepted client connection
[ Core    ] [2018-03-13T15:57:47] ERROR: invalid message from client "SCOTT-HP1310": CALV
[ Router  ] [2018-03-13T15:57:47] debug: Error reading from core server: End of file
[ Router  ] [2018-03-13T15:57:47] debug: Terminating core server read loop
[ Core    ] [2018-03-13T15:57:47] NOTE: new client disconnected
[ Service ] [2018-03-13T15:57:49] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:57:49] debug: profile screen status changed, screenId=12652 Connected->Connecting
[ Service ] [2018-03-13T15:57:49] debug: profile changed, storing local copy
[ Router  ] [2018-03-13T15:57:57] debug: ClientProxy: Received client connection for SCOTT-HP1310 from screen 12652
[ Core    ] [2018-03-13T15:57:57] NOTE: accepted client connection
[ Core    ] [2018-03-13T15:57:57] DEBUG: received client "SCOTT-HP1310" info shape=0,0 5120x1440 at -13541,32766
[ Core    ] [2018-03-13T15:57:57] DEBUG: active sides: 4
[ Core    ] [2018-03-13T15:57:57] NOTE: client "SCOTT-HP1310" has connected
[ Service ] [2018-03-13T15:57:58] debug: comparing profiles, id=6309 this=v86 other=v86
[ Service ] [2018-03-13T15:57:58] debug: profile screen status changed, screenId=12652 Connecting->Connected
[ Service ] [2018-03-13T15:57:58] debug: profile changed, storing local copy
[ Core    ] [2018-03-13T15:58:57] INFO: switch from "SKOW" to "SCOTT-HP1310" at 0,675
[ Core    ] [2018-03-13T15:58:57] INFO: leaving screen
[ Core    ] [2018-03-13T15:58:57] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:58:57] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:58:57] DEBUG: ignored screen "SKOW" update of clipboard 0 (unchanged)
[ Core    ] [2018-03-13T15:58:57] DEBUG: open clipboard
[ Core    ] [2018-03-13T15:58:57] DEBUG: close clipboard
[ Core    ] [2018-03-13T15:58:57] DEBUG: ignored screen "SKOW" update of clipboard 1 (unchanged)
[ Core    ] [2018-03-13T15:58:57] DEBUG: sending clipboard 0 to "SCOTT-HP1310"
[ Core    ] [2018-03-13T15:58:57] DEBUG: sent clipboard size=261
[ Core    ] [2018-03-13T15:58:57] DEBUG: sending clipboard 1 to "SCOTT-HP1310"
[ Core    ] [2018-03-13T15:58:57] DEBUG: sent clipboard size=261
[ Core    ] [2018-03-13T15:58:57] DEBUG: dropped bogus delta motion: +1724,+7
[ Core    ] [2018-03-13T15:58:59] INFO: switch from "SCOTT-HP1310" to "SKOW" at 2632,853
[ Core    ] [2018-03-13T15:58:59] INFO: entering screen
[ Config  ] [2018-03-13T16:01:56] info: Sending log file...

 

Share this post


Link to post
Share on other sites

Ryan, I assume you too are sharing from your desktop (server) to the laptop (client)? One similarity we share plus the client is wireless.
Likewise, I have very little resource usage except for ram (at times) which can be up as much as 70%. Though even down at 50% the issue persists.

Share this post


Link to post
Share on other sites

I got nothing.

I'll be interested to see what support might say. Perhaps one of the other moderators will offer us a direction

BTW, guys, next time around, it keeps the forum a little cleaner if you just post the link to the log files. We can look at the in a separate browser window.

  • Like 1

Share this post


Link to post
Share on other sites

In our experience so far, the most common causes of lag are high DPI mice or high-resolution screens. What kind of mouse are you using (model, wired/wireless, bluetooth, etc.)? Is the lag consistent across both machines or only on the client or server (and have you tried sharing from the other)? 

Share this post


Link to post
Share on other sites
3 minutes ago, Sarah Hebert said:

In our experience so far, the most common causes of lag are high DPI mice or high-resolution screens. What kind of mouse are you using (model, wired/wireless, bluetooth, etc.)? Is the lag consistent across both machines or only on the client or server (and have you tried sharing from the other)? 

 

I am personally using Steel Series Rival 700 mouse @ 800 CPI.

 

My environment:
Windows 10 Desktop 

  • 2 Monitors 3480x2160 (although problem persists as 1920x1080)
  • Wired ethernet connection


Macbook Pro laptop

  • 1 Monitor 2560x1600 
  • Wireless only (5g)

 

 

Share this post


Link to post
Share on other sites

Hi Sarah,
It's Scott (from emails).

The monitor is Samsung, I think it's 36". It runs at 2560x1440. As does the 13" laptop screen attached to it though I usually never use that screen when connected to the larger monitor. The mouse is a logitech m510 (https://www.logitech.com/en-us/product/wireless-mouse-m510) I do not believe it is high DPI. The desktop monitor is Samsung 1920x1080.

With the second machine being the laptop, it's not all that easy to share from it to the desktop with the desk layout. I do know that when I use the laptop touchpad and keyboard on the laptop, there is no lag, when I use the desktop keyboard and mouse on the desktop, there is no lag. When I use the desktop keyboard and mouse on the laptop via Synergy, there is lag.

If it is the high DPI monitor - is that something that can be resolved or due to that technology it is not possible? I recall using that monitor over the last year and it not being as significant of an issue until more recently.

Thanks!

-Scott

Share this post


Link to post
Share on other sites

One last thing to note. On the larger monitor I do run PIP with a smaller screen embedded in the lower left corner. That layout effectively looks like:

Desktop Computer/Screen (DVI to Samsung 1920x1080) on the left
Desktop Computer with DVI to Samsung PIP window (720x576) "to the right" of the Desktop Main Monitor
Laptop Computer with HDMI input to main portion of Samsung (2560x1440)
Laptop 13" screen to the far right at 2560x1440

I recognize that is a bit more on-traditional setup. I can play around without PIP on and see if that makes a difference, though curious to know more about the issues with higher dpi resolutions.

Thanks!
-Scott

Share this post


Link to post
Share on other sites

i guess it might be related to this:

 

Share this post


Link to post
Share on other sites

I'm still using 1.8, and there is no lag at all so, it's something with the latest release. I cannot update to the 2.0 until I stop seeing stuff like this. :(

Share this post


Link to post
Share on other sites

I should note I do experience lag on 2.0.7 but had to roll back to 1.8 and that solved the lag issue, just to clarify that I am experiencing this issue on 2.0.7 and that's the reason I am using 1.8

Share this post


Link to post
Share on other sites
Posted (edited)

I've finally gotten Synergy 2 to actually connect (thanks Nick and Sarah for the LITERALLY nonstop support ticket since 2.0.4) and now my mouse is fine on my primary pc but on my secondary PC (a shitty laptop) its running around like its a combination of "through molasses" and a supermario ice level...

You know the pointer is slower then the mouse movement SHOULD be, and then it overshoots drastically since it cant slow down propperly... Back when i was rolling 1.8.8 i never had either of these issues. But now that i have it finally working i am inclined to put the effort in to get it to be right...

https://synergy-logs.symless.com/7dd94274f35de1a4832b0a433b29718d/logs/22605-2018-03-15T14-42-53.log (log from my main machine)

Edited by FireFrenzy
  • Like 1

Share this post


Link to post
Share on other sites

I am curious to hear from Symless on this particular issue and how much effort is being put towards it. Perhaps I'm wrong but any new feature development is pretty worthless when the product is nearly unusable. I'd like to know if this is a problem that can't be fixed because it is hardware related, or perhaps they've not figured out yet how to resolve it?

I am happy to invest time to help them resolve this but the lack of response or days in between responses does not inspire confidence. The responses are often vague and unhelpful. Wouldn't it be better for all parties to actually engage in some conversation about this problem, or are am I just one of a very few that are struggling with it?

 

Share this post


Link to post
Share on other sites

I don't have the issue you describe so here's another vague reply:

Version 2.0.8 should drop in the next few days. It will be worth a try for you to check the lag issue.

Share this post


Link to post
Share on other sites

Thank you, will certainly give it a try. I'd just like to hear that they're actually and actively trying to resolve it. If it's the result of high dpi monitors, do they have one in house? Do they see lag with it? Can they repeat it and identify what's causing it in order to then define a plan to resolve it? From the outside looking in it sounds like they're more focused on adding new config screen features and I've not heard or seen anything to indicate they have a plan for this.

Share this post


Link to post
Share on other sites

I only know that I've seen some discussion among the developers about the lag issue. It seems it is a  problem with multiple underlying factors. I thought I'd let you know that it is not being ignored.

My only mouse issue has been a sort of stutter when one screen and entering the other. Very subtle, maybe 1/10 of a second and ignorable. Only on 2 screens while the other margins have been smooth. I'm going to be interested to see if that trivial hickup is still there in 2.0.8. I'm getting indications it should drop in the next few days.

 

Share this post


Link to post
Share on other sites

Thank you again, good to know. Mine matches FireFrenzy's post above - molasses immediately followed by mario on ice. It then gets so bad it just disconnects and my keyboard and mouse are thrown back to the main server side screen. This of course is sometimes an issue as Typing along then impacts what was open on that screen.

I am happy to work directly with them if they need more feedback, testing, etc. to nail this one. Feel free to let them know.

Share this post


Link to post
Share on other sites

:/ the next version is worth a shot. I haven't seen change logs that I usually have access to, so...I dunno.

Share this post


Link to post
Share on other sites

Running 2.0.8 and so far lag seems to be looking pretty good. Will report back as I continue to use it, fingers crossed!

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