RE: CDATA leaks in XmlRpc client classes

2002-11-11 Thread Glen Lewis
Sounds good - maybe the XmlRpc class could even have a configurable maximum size for the CDATA buffer. -Original Message- From: [EMAIL PROTECTED] [mailto:dlr@;finemaltcoding.com] Sent: Monday, November 11, 2002 2:50 PM To: Glen Lewis Cc: [EMAIL PROTECTED] Subject: Re: CDATA leaks in

Re: CDATA leaks in XmlRpc client classes

2002-11-01 Thread Ryan Hoegg
Unfortunately we don't have any important people on this project. We are all peasants. :( j/k we'll look into it. If you have the time could you create a bug report? Even better would be a test case illustrating the problem. Bug reports go here: http://nagoya.apache.org/bugzilla/enter_bug.c

CDATA leaks in XmlRpc client classes

2002-11-01 Thread Glen Lewis
XmlRpc.parse() initializes the "cdata" field and then clears it ( by calling setLength(0) ) upon subsequent calls to parse(). This results in a memory leak between calls to parse(), since the "cdata" field persists as long as the XmlRpc object. In my particular case, a large logfile was being