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

GCP Issue 9 - memory leak #6

Open
cverges opened this issue Aug 27, 2013 · 0 comments
Open

GCP Issue 9 - memory leak #6

cverges opened this issue Aug 27, 2013 · 0 comments

Comments

@cverges
Copy link
Owner

cverges commented Aug 27, 2013

Reported by kab...@gmail.com, Jul 1, 2010
There is a memory leak in the spawn command.
The current Expect4j class is associated with each new spawnId via interp.setAssocData, but never cleared.
This leads to a memory leak, if we spawn a lot in the same session.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cverges