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.

Sign up for GitHub

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

Jump to bottom

Memory leak #149

Closed
kpdyer opened this issue Jul 18, 2014 · 0 comments
Closed

Memory leak #149

kpdyer opened this issue Jul 18, 2014 · 0 comments
Assignees
@kpdyer
Labels
bug
Milestone
0.2.16

Comments

@kpdyer
Copy link
Owner

kpdyer commented Jul 18, 2014

When running fteproxy for long periods of time (weeks) the fteproxy python process consumes all available memory on a system.

Unfortunately, I have no specific details on how to recreate this.
@kpdyer kpdyer added this to the 0.2.16 milestone Jul 18, 2014
@kpdyer kpdyer self-assigned this Jul 18, 2014
@kpdyer kpdyer modified the milestones: 0.3.0, 0.2.16 Jul 19, 2014
@kpdyer kpdyer added the bug label Jul 19, 2014
@kpdyer kpdyer modified the milestones: 0.2.16, 0.3.0 Jul 19, 2014
@kpdyer kpdyer closed this as completed Jul 19, 2014
kpdyer added a commit that referenced this issue Jul 19, 2014
@kpdyer
Close #149: no need for self._workers, merely a growing list
66aa3c2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kpdyer kpdyer

Labels
bug
Projects
None yet
Milestone
0.2.16
Development

No branches or pull requests
1 participant
@kpdyer