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 on controlling side #10

Closed
dzafman opened this issue Mar 23, 2015 · 11 comments
Closed

Memory leak on controlling side #10

dzafman opened this issue Mar 23, 2015 · 11 comments
Assignees

Comments

@dzafman
Copy link

dzafman commented Mar 23, 2015

I noticed high memory usage (over 1GB) on controlling side after app is restarted the memory usage is 21.5MB. Every time I connect and disconnect the memory usage jumps up by about 60MB.

@tjd2002
Copy link

tjd2002 commented Mar 23, 2015

I see something similar. Real memory usage goes up by 9MB every time I move the cursor from the master to the slave machine. Using teleport 1.2, and with OS X 10.10.2 on both machines.

@dzafman
Copy link
Author

dzafman commented Mar 23, 2015

I should have been clearer. I am also running Teleport 1.2 on 10.10.2 on both controlling and controlled machines.

@forty4
Copy link

forty4 commented Mar 24, 2015

Memory leaks on both sides.

@tomads
Copy link

tomads commented Mar 24, 2015

Yep. Confirmed. Memory leaks on BOTH sides!

@abyssoft
Copy link
Contributor

Pretty bad indeed. Probably due to my conversion to ARC. Didn't have much time to test it, I wanted to open source it asap.

@crcastle
Copy link

@tjd2002 sorry about that. Created new ticket #14 and deleted it from this thread.

@abyssoft
Copy link
Contributor

abyssoft commented Apr 2, 2015

That's gonna be my next priority for 1.2.1.

@abyssoft abyssoft self-assigned this Apr 2, 2015
@abyssoft abyssoft added this to the v1.2.1 milestone Apr 2, 2015
@atljeremy
Copy link
Contributor

+1 to the memory leaks

atljeremy added a commit to atljeremy/teleport that referenced this issue Apr 10, 2015
…ndows were being created and added to an NSSet and never removed/released johndbritton#10
@sebastiansibelle
Copy link

@abyssoft Looks like you merged a fix for this issue, do you have a timeframe on making a release/hotfix? Appreciate that you are probably very busy!

@abyssoft
Copy link
Contributor

I will try to do that next week.

@abyssoft
Copy link
Contributor

Fixed in 1.2.1.
Thanks Jeremy!

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

No branches or pull requests

8 participants