Hi gents,
I've never seen this behavior before, but this is what happened recently.
2 Endpoints
I did shutdown my Win10 station, came back the next day, and my macbook was out of memory (pausing all apps).

Suspect it did not handle the server shutdown properly, but I've done this multiple times and it never happened before.
I couldn't grab much logs/information as my macbook was completely unresponsive.
Thanks for the report. Unfortunately there's a lot of legacy memory management in Synergy. This is something we hope to address once we move to a new build process (VS2015, Qt etc.). In the meantime, if you notice or determine a way to trigger this behaviour specifically, let us know.
Perhaps next time you're shutting down for the night, and you don't have anything important running on your Mac, you could try and reproduce this memory leak by just doing what you did before?
I'll try to add/get information if I reproduce it.
I had this problem in a nightly build so I rolled back to the stable release [1.8.2-stable-36cd521] and do no longer see a problem on client. I will return if and when it pops up again on my setup.
Mac Pro (client)
MacBook (server)
@tsugliani @cyberea
Any update on this issue?
@XinyuHou haven't reproduced it yet, maybe it was only a 1 time thing for me. (I'll update this if it ever happens again)
@XinyuHou @tsugliani I haven't seen it pop up since my last comment.
Seems to be working well though! Even when I leave the work place where MacPro (client) resides, leaving it on standby and putting MacBook (server) to sleep. I come back the next day with laptop, wake it up and everything works well right from where I left off without having to do anything.
It appears that I spoke too soon. I came in this morning and OS had paused many application processes because it had run out of memory.
I just terminated the process and restarted the application. I have no further evidence or theories as why it happened this time around.
Any memory leaks being experienced with 1.8.3 or 1.8.4 RC3?
I am seeing a memory leak on 1.8.8 built April 6 2017. I arrived to my desktop today to see memory and swap usage to the point of nearly OOMkilling things (and instead, just making the desktop horrendously slow as memory tried futily to swap in and out of my NVMe flash) ..
Before using top from console to kill the process:

After:
