Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak in GUI on Windows caused by logging #4577

Closed
speaker opened this issue Apr 24, 2015 · 14 comments
Closed

Memory leak in GUI on Windows caused by logging #4577

speaker opened this issue Apr 24, 2015 · 14 comments
Labels
Milestone

Comments

@speaker
Copy link
Contributor

speaker commented Apr 24, 2015

Issue seen in Synergy 1.7.1 running on a windows 7 enterprise 64bit synergy server connected to an 10.10.3 iMac synergy client.

The synergy service continues to allocate physical memory (private) but doesn't appear to free the memory resource. Resource monitor can track the usage:
synergy_mem_use

The allocation appears related to switching from server to client and back. The problem appears worse when the switching back and forth is quick. (10 quick back and forth will consume more memory than slowly moving back and forth 10 times.)

@legonigel
Copy link
Contributor

@speaker I can get to 100MB of memory usage on Linux in a not too much time as well. It only affects the synergy executable, not synergys. It is related to the logging. If you change the logging level to note, the memory usage decreases significanlty. See #4363 and #4341.
image

@legonigel
Copy link
Contributor

It could also be related to #3335.

@andreialecu
Copy link

I've had memory usage issues with synergy for the past few years. Only thing I can do is completely uninstall it when I don't need it. Closing synergy itself does not clear the leaks, and the more uptime I have, the more they build up.

The leaks are extremely hidden, they don't even show up in taskmgr. I can only see them in RamMap, with thousands of synergys.exe and syntool.exe processes running and taking 20K each.

Memory Leak

Note that this screenshot above was taken on a PC that hasn't even used synergy at all since boot, it was simply running in the background - with an uptime of 12 days.

@nbolton
Copy link
Member

nbolton commented May 15, 2015

Duplicates #4341

@nbolton nbolton closed this as completed May 15, 2015
@nbolton nbolton modified the milestones: v1.7.3-stable, v1.7.4-stable May 15, 2015
@nbolton nbolton self-assigned this May 20, 2015
@nbolton nbolton changed the title Memory Leak in synergy.exe on windows Memory leak in GUI on Windows caused by logging May 23, 2015
@nbolton nbolton removed their assignment Oct 12, 2015
@sccovey
Copy link

sccovey commented Feb 13, 2019

I have experienced this exact issue on Windows 10 running Synergy 1.10.1-stable-8941241e

RampMap is showing me thousands of syntool.exe and synergys.exe instances all sitting at 28k

the synergy log just keeps repeating the following lines:

synergys.exe: no configuration available
[2019-02-13T00:17:13] ERROR: failed to launch, error: process immediately stopped
[2019-02-13T00:17:13] INFO: backing off, wait=10s, failures=9432
[2019-02-13T00:17:23] INFO: starting new process
[2019-02-13T00:17:24] INFO: activeDesktop:Default
[2019-02-13T00:17:24] INFO: starting new process
[2019-02-13T00:17:24] INFO: drag and drop enabled
synergys.exe: no configuration available
[2019-02-13T00:17:25] ERROR: failed to launch, error: process immediately stopped
[2019-02-13T00:17:25] INFO: backing off, wait=10s, failures=9433
[2019-02-13T00:17:35] INFO: starting new process
[2019-02-13T00:17:35] INFO: activeDesktop:Default
[2019-02-13T00:17:35] INFO: starting new process
[2019-02-13T00:17:35] INFO: drag and drop enabled

@mazend
Copy link

mazend commented Jul 15, 2020

I have experienced this exact issue on Windows 10 running Synergy 1.10.3-stable-ca35737a

이미지 007

In addition I'm suffering from High cpu usage of System and WMI Provider Host processes with memory leakage.
I'm suspecting synergy program now.

The issue continuously happens after turning on computer for about 2~3 days even though I didn't run the synergy program.

Anyways I downloaded the latest synergy v. 1.11.1-stable-55ec3105.

I will check what would happen.

@charles-peter-nystrom
Copy link

I'm running into the old handle leak on 1.11.1-stable-55ec3105 running on Windows 10.0.18362, synergyd hit 280k handles in just under 10 hours.

@digitalsanity
Copy link

Debugging Windows 10 memory issues with 32GB RAM and traced it back to synergys also via rammap.

@andreacndn
Copy link
Contributor

@digitalsanity we have fixed a number of memory leaks is 1.13.0, could you please test if the release candidate solves your problem?
https://rc.symless.com/synergy-1.13.0-rc2/synergy-1.13.0-rc2-windows-x64.msi

@mazend
Copy link

mazend commented Dec 15, 2020

Hi All,
Here is my story.
The old version synergy v. 1.11.1-stable-55ec3105 didn't solve the problem.
I updated my ram from 16GB to 32GB but the issue still happened.
So.. I had deleted synergy long long ago.

I've just installed the latest version, 1.13.0.
I think I can know the result in 2~3 days.
I will test it in synergy idle status because the issue happened even in idle status.

I attached pictures when I started test.

이미지 044
이미지 046

@andreacndn andreacndn reopened this Dec 15, 2020
@mazend
Copy link

mazend commented Dec 17, 2020

I'm back.
I didn't turn off my laptop for two days and used the laptop during my waking hours.
It seems the issue was resolved.
The numbers of handles in synergy.exe and synergyd.exe are within the normal range.
I attacked related picitures.

이미지 098
이미지 097

@andreacndn
Copy link
Contributor

@mazend thanks for the update!
Looks great, will keep this issue open for few more days to be 100% sure it's all fixed.

@mazend
Copy link

mazend commented Dec 23, 2020

Here is another test result.
I was going to keep my laptop turned on but.. unexpected windows update reboot my laptop.
so.. It's synergy idle test for 3 days.
It seems it's good.

I would confirm the memory issue I had experienced before was resolved.
(I'm not sure whether other memory leak issue is exist or not)

이미지 062
이미지 063

@andreacndn
Copy link
Contributor

Thanks for the update!
I'll close the issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants