this should be a response to the last posting
with the same topic but parserversion 1.5.1 :-)

very similar thing:

Xerces C++ Bug Report:

Xerces-C++ version number:      1.7.0
Platform:        AIX
Operating system and version number:    4.3.3 Maintenance Level 9
Compiler and version number:    xlC 3.6.6.0
The XML document (or excerpt) that failed:      show description
The C++ application code that failed    show description
Whether you built the Xerces-C++ library
    yourself or used the binary distribution:   both testet, same error

What happened:

As you told me before where I used Xerces 1.5.1 now I upgradet to 1.7.0. I am using 
the SAX2 parser.
There is a BIG difference and there are not so much memory leaks in 1.7.0 !!!
When parsing so about 1,5 GB of XML version 1.5.1 increases up to 250 MB (and more) 
needed Memory (by process / parser) and same source with 1.7.0 increases too (but not 
so much and fast, so the process comes to more, but there are bugs left.) So with 
version 1.7.0 with the same XML as basis for parsing the processmemory increases up to 
45 MB (and more as you are going on to parse...)
So there is greatly effort done, but too something left. I hope the next version will 
remove some leaks, because my programm has to parse very much big data files (so 16 GB 
could be normal size :-) and I have to look that there is not too much memory waste 
done, cause there should run multiple instances of my process.
Would it be a good idea to test, if the actual development version is better than the 
stable release (whats about the *stable" and the memory leaks) ?
Thanks for any comment.

Another thing: how could I response to a posting in this *group"? (i have nowhere find 
such a *response" button?

My code is the same as in the last postings.... (topic memory leaks)


Stefan Hummert (SIS/hu)

Schober Informationssysteme GmbH
Max-Eyth-Stra�e 6-10
D-71254 Ditzingen
Tel.:   07156-304-493
Fax:   07156-304-310
EMail:  [EMAIL PROTECTED]


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

Reply via email to