On this memory leakage problem, it does seem the case that memory leaks come
into releases with new functionality.  However we have had very good
operation in 1.3 and still have customers using this.  We do re-test using
bounds checker for each release which pretty soon establishes the presence
of any problems (providing we use a range of messages sizes from tiny
through to 10MB xml files).  Once this simple test is established we have
then had very good performance.

Actually if you compiled the 1.3 release with debug the memory management
facilities in the XERCES libraries themselves reported our own memory
leakage problems!!!  That is an excellent facility, though I have not used
it much recently!

Nick

-----Original Message-----
From: Don Mastrovito [mailto:[EMAIL PROTECTED]]
Sent: 18 October 2001 17:35
To: [EMAIL PROTECTED]
Subject: Re: XercesC++ vs MSXML on Windows platform


David,

I had a similar experience with MSXML3/4.  I originally used MSXML because 
it was the native XML parser for windows and in many respects, provides 
richer (more functional) APIs.  However the memory leakage and deployment 
problems caused me to seek other alternatives.  With Xerces, the most 
common complaint has been in the area of memory leaks, but the problems are 
being addressed in a timely fashion.

Don

At 05:25 PM 10/18/2001 +0200, you wrote:
>                         Hi all,
>
>         I'm using MSXML4 on a NT platform to parse and modify XML
documents.
>I'm testing my application and have memory problems. It seems that the
>application doesn't release my object. If I execute my application many
>successive times, I have no more memory available!!
>         I have check all my memory allocations and I release everything!
>Does someone know if MSXML has known problems with memory use? Does Xerces
>make a better use of memory?
>
>         Thanks for help
>
>         David.
>
>DELGRANCHE David
>SOGITEC Industries
>Division Documentation et Syst�mes
>24 avenue Lavoisier
>BP 7408
>35174 BRUZ cedex
>T�l: 02.99.05.34.25
>Fax: 02.99.05.34.05
>email: [EMAIL PROTECTED]
>
>--------------Interscan------------- (on the network)
>
>email-body was scanned and no virus found
>------------------------------Traite par ISVW---------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


************************************************************************* 
This message contains privileged and confidential information intended 
only for the use of the recipient named above. Its contents do not 
constitute a commitment by Strategic Thought Limited ("Strategic 
Thought") unless separately endorsed by an authorised representative 
of Strategic Thought. 
 
Any use, dissemination, distribution, reproduction or unauthorised 
disclosure of this message is prohibited. If you receive this message 
in error, please notify the sender immediately and delete it from your 
computer systems. 
 
Any views expressed in this message are those of the individual sender 
and may not necessarily reflect those of Strategic Thought. 
 
Strategic Thought believes this e-mail and any attachments to be virus 
free. However, the recipient is responsible for ensuring it is virus 
free and Strategic Thought do not accept any responsibility for any 
loss or damage howsoever caused from use of this e-mail, attachments 
or contents. 
************************************************************************* 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to