Bug fix for 2827039
Status: Beta
Brought to you by:
dcrowley
Menu
▾
▴
#20 Bug fix for 2827039
We recently discovered an apparent memory leak in EasySoap. We create and cache a SOAPProxy object and re-use it. Every call to Execute() would leak the parsed XML stream from the previous invocation of Execute(). I tracked this down to the "pool" holding the xml snippets in the SOAPBody in SOAPResponse not being released. All of the memory was properly released when the SOAPProxy was destroyed.
Our bug find is very similar to #2827039, reported on 2009-07-25.
I am attaching a fix against 0.6.0 (we have not updated to 0.8.0 yet). I hope that it serves others well.
Note: Our easysoap is a vendor branch in subversion. The patch is against my own branch, not against any CVS revision hosted on source forge. However, the patch should help anyone else trying to patch 0.8.0. Basically, in SOAPProxy::Execute() you need to invoke "Reset()" on the "body" of the previous "response". There is probably a better solution, but ours seems to work.
ps- is this project being actively maintained anymore?
Patch against 0.6.0