Anurag,
you are importing a DOM tree into an existing DOMDocument (returned by
the external getDocument() function call); we don't know what you are
doing with this DOMDocument object, but if you don't release it, that's
where the memory leak is.
Alberto
Anurag Jain wrote:
This implementati
Hi Anurag,
Anurag Jain <[EMAIL PROTECTED]> writes:
> We are especialy interested in fixing this with xerces 2.7
You have a better chance of having your problem assessed and fixed
if you provide a small, compilable test case (with sample XML file
if required) that reproduces the problem. Providin
This implementation (code below ) leaks memory on solaris (when we call it
serveral times) with xerces 2.7 and also xerces 2.8 , does anyone see a
problem with it ...
if we remove the DOMDocument importNode function call it stops leaking ..We
are especialy interested in fixing this with xerc
