-
Notifications
You must be signed in to change notification settings - Fork 615
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
Potential memory leak #485
Comments
your probably right. using symbols internally might not be necessary and i have to look into that. |
Hi, @rubiii , @vanderhoorn This does cause memory leaks in our program, we have a program which will read a huge data from a webservice, when it run a day after it reached 8G memory footprint. |
we can't change the symbols for version 2, but i'll make sure that version 3 doesn't cause such problems. |
No problem. |
Added a task for this in the version 3 TODO list #473 |
As you may know, while strings are garbage collected, symbols are not.
In the
build_elements
on line 27 all element names are symbolized (name.to_sym
). So if you use the savon gem intensively in an application and you use a lot of different element names, the memory usage of the application will increase substantially over time. I don't think using symbols in this case is a wise approach.The text was updated successfully, but these errors were encountered: