memory leaks in SWIG interface files
|Assignee:||Redmine Admin||% Done:|
There are memory leaks in the SWIG interface files (both Ruby and Python). It seems to be caused by the code of the typemaps.
In Gonzalo Garramuño's opinion, "malloc/memcpy should not be used. That memory allocated by malloc is afaik never being released (and cannot be released sanely by a ruby free_func as it was allocated as block)."
#1 Updated by Andreas Schröder over 9 years ago
- Status changed from New to In progress
Seems to be fixed for Ruby. See http://drqueue.org/cwebsite/drqueue_community/comments.php?DiscussionID=493 for progress on this bug.
#3 Updated by Redmine Admin over 9 years ago
- Status changed from Fixed to Feedback
- Resolution deleted (
That's not a resolution for Python, I guess. As long as there are Python bindings, bug should not be marked as fixed if it's not fixed for them.
I'd like to know more opinions regarding the memory allocation issue (regarding Python) as I share the feeling of it being caused by the fact of being allocated as a block and not individually.
I do not know how to do it properly and would like to know to make it right.