From: Martin K. <mar...@fe...> - 2009-04-29 16:52:20
|
Hi, I haven't seen this behavior yet, but I'd sure be interested in a fix ;-). To narrow down the scope, you could try XML::Parser::Lite as XML parser backend - if the memory leak disappears, it's a XML::Parser issue. Regards, Martin Am Montag, den 27.04.2009, 15:20 +0200 schrieb Levente Tamas: > Hi, > > yesterday we discovered a problem using soap::lite, namely on 64bit > Fedora 10 it is leaking memory about 100bytes/request, however it is > working perfectly on 32bit Fedora 10. I installed the latest from CPAN. > The problem is now narrowed down to the requests made with ->result at > the end, letting the module handle the deserialization of the packet. I > checked it by using a simple test pinging a pokersource network several > times a second for a while. > Once I initialize the object with outputxml('true'), the leak is gone, > but naturally I can't call ->result on the returning string. > > did anyone noticed the same problem? > The worst part is that even if I destroy our object that has the > soap::lite reference, the memory doesn't get cleaned up, so I think it > points a little out of perl's range. I suspect a bug somewhere in the > XML parser. > > Any idea? > Levente > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ Soaplite-devel mailing list Soa...@li... https://lists.sourceforge.net/lists/listinfo/soaplite-devel |