Documentation should state that one needs to explicitly free xdoc objects
Closed this issue · 3 comments
robertfeldt commented
I had problems with a long-running optimization that was leaking memory. The cause seems to be that xdoc objects it created in each function/fitness eval needs to be explicilty freed. Details in this google groups thread:
https://groups.google.com/forum/#!topic/julia-users/ycFiuyjSgdA
Until finalizers are added to the code base, I suggest the LightXML front page is updated to clearly state that the user must take care to free objects.
tkelman commented
If you have a suggested wording, a PR would be welcome.
robertfeldt commented
Not sure of the wording but at least there is now a proposed note about it in the README.