-
-
Notifications
You must be signed in to change notification settings - Fork 252
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 #229
Comments
Once I get the file down loaded I'll take a look. The close should free memory. On April 18, 2015 1:40:14 PM PDT, Marco Colli notifications@github.com wrote:
|
To reproduce the issue you can use this script: |
Found out that this causes the issue:
While this is correct and doesn't waste memory:
|
I believe this is fixed a release or two ago. |
@ohler55 Sure, you have fixed it in version 2.12.4 a few days after my message. Thanks a lot! Now this issue can be closed. |
Even if I already mentioned this problem in #228 saying that I get a "Killed: 9" this is a totally independent problem from the segmentation fault and I think it deserves its own ticket.
Further investigating the "Killed: 9" I discovered (quite obvious) that the ruby process steadily increases memory usage.
The line responsible for this issue is:
In fact by simply substituting it with
I get no problems with memory usage. (The above lines produce different objects, but this is not a problem, since in this demonstration
@entity
is never used. Also I could have simply removed the line instead of substituting it, but I have done this to prove that is not simply a problem with the garbage collector)Adding
@entity.close
after the open doesn't solve the issue.The text was updated successfully, but these errors were encountered: