search

Arzaroth / python_rapidxml

python bindings for RapidXml, a C++ XML parsing library
MIT License
6 stars 2 forks source link

Memory leaks #7

Open abagoo opened 5 years ago

abagoo commented 5 years ago
  1. All calls to PyArg_ParseTupleAndKeywords that unpack strings ("s*") need to call PyBuffer_Release(). Currently all buffers passed into rapidxml extension leak.
  2. rapidxml_DocumentObject_dealloc never gets called by python 3.6.1. As a result, all the memory allocated by memory_pool leaks. That can be resolved in python 3 by switching order of RapidXml base types.
Arzaroth commented 5 years ago

Thanks for the heads-up. I can't say that I have been taking care of this project lately. I'll try to fix at least the first point you raised in the near future, but don't expect much else. I'll happily merge any pull request, if you're willing to give it a go.

skiwithuge commented 5 years ago

hi all, @abagoo could you please give me more information about your proposed solution? I've tried to contact you and i didn't find any email address

Thank you

Amedeo91 commented 5 years ago

Hello all,

we are having a similar issue of memory leak using with python 3.5 actually. Could it be related to problem 1 that @abagoo identify?

Thank you all. Amedeo