Wake W7 server from lock, crashing synergys.exe (1.8.8) (64-bit)

[jim symolon]

W7 acting as the server, 64-bit, 1.8.8-stable-25a8cb2.  Client is Linux Mint (64-bit) running same version

Lock screen, come back and wake, synergy crashes but process still running  Repeatable (lock screen, unlock).  Note, Linux side doesn't lock/unlock w/ W7 server.

Unhandled exception at 0x02050d80 in synergys.exe: 0xC0000005: Access violation at location 0x0000000002050d80.

Problem signature:
  Problem Event Name:    BEX64
  Application Name:    synergys.exe
  Application Version:    0.0.0.0
  Application Timestamp:    58ca90ae
  Fault Module Name:    StackHash_5734
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Offset:    0000000002079b20
  Exception Code:    c0000005
  Exception Data:    0000000000000008
  OS Version:    6.1.7601.2.1.0.256.4
  Locale ID:    1033
  Additional Information 1:    5734
  Additional Information 2:    5734ab4258e07c565d71aa3aa93bf8ac
  Additional Information 3:    6762
  Additional Information 4:    6762d95398fd4357ac56303048961c06

 

>    0000000002050d80()    
     synergys.exe!000000013fb33d46()     
     [Frames below may be incorrect and/or missing, no symbols loaded for synergys.exe]    
     synergys.exe!000000013fb33e84()     
     synergys.exe!000000013fb3d8de()     
     synergys.exe!000000013fb16f09()     
     synergys.exe!000000013fb16f92()     
     synergys.exe!000000013fb187e3()     
     synergys.exe!000000013fb16cb4()     
     synergys.exe!000000013fb29f67()     
     synergys.exe!000000013fb1893e()     
     synergys.exe!000000013faf205e()     
     synergys.exe!000000013fb2c122()     
     kernel32.dll!0000000076df59cd()     
     ntdll.dll!0000000076f2a561()     

[2017-06-16T13:22:12] NOTE: client "jbsymolo-l3" has disconnected
[2017-06-16T13:36:19] WARNING: detected application not running, pid=15436
[2017-06-16T13:36:20] INFO: backing off, wait=2s, failures=1
[2017-06-16T13:36:22] INFO: starting new process
[2017-06-16T13:36:22] INFO: activeDesktop:Default
[2017-06-16T13:36:22] INFO: starting new process
[2017-06-16T13:36:22] INFO: drag and drop enabled
[2017-06-16T13:36:22] NOTE: started server, waiting for clients
[2017-06-16T13:36:22] INFO: watchdog status: ok
[2017-06-16T13:36:22] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-06-16T13:36:23] INFO: accepted secure socket
[2017-06-16T13:36:23] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD

[2017-06-16T13:36:23] NOTE: accepted client connection
[2017-06-16T13:36:23] NOTE: client "jbsymolo-l3" has connected
[2017-06-16T13:38:15] NOTE: disconnecting client "jbsymolo-l3"
[2017-06-16T13:38:15] NOTE: client "jbsymolo-l3" has disconnected

(LOCKED/ UNLOCKED HERE ?  ... when duplicating, i see the log stop here)

[2017-06-16T13:40:09] WARNING: detected application not running, pid=30084
[2017-06-16T13:40:10] INFO: backing off, wait=2s, failures=1
[2017-06-16T13:40:12] INFO: starting new process
[2017-06-16T13:40:12] INFO: activeDesktop:Default
[2017-06-16T13:40:12] INFO: starting new process
[2017-06-16T13:40:12] INFO: drag and drop enabled
[2017-06-16T13:40:12] NOTE: started server, waiting for clients
[2017-06-16T13:40:12] INFO: watchdog status: ok
[2017-06-16T13:40:14] INFO: OpenSSL 1.0.2 22 Jan 2015
[2017-06-16T13:40:14] INFO: accepted secure socket
[2017-06-16T13:40:14] INFO: AES256-GCM-SHA384       TLSv1.2 Kx=RSA      Au=RSA  Enc=AESGCM(256) Mac=AEAD

[2017-06-16T13:40:14] NOTE: accepted client connection

[2017-06-16T13:40:14] NOTE: client "jbsymolo-l3" has connected

synergy.log

[Paul Suarez]

Hi @jim symolon. I'm still coordinating with our developers on this. Please bear with us. 

[jim symolon]

No problem.  It's just a nag message - doesn't disrupt my work (too much).

[Paul Suarez]

Hi @jim symolon. Please try to set your Server machine's elevation as "always." 

1. Stop the Server
2. Click Edit
3. Click Setting
4. Set Elevate to Always
5. Click OK ***try to restart Synergy first by quitting it and re-opening***
6. Click Apply or Start

Let us know how it goes.

[Stuart Walker]

I had this error too (same version) and changing the setting to "Always" seems to have fixed it....