These aren't leaks. These are setup of one time only static/global data
that only happen once you initialize. They will not ever happen again
within the same process and just live for the life of the process. Its no
different than had they been created by global objects, in which case you
just wouldn't have seen the becasue they happened before the main();
however, we can't use global objects because that's not portable. So, if
you are using the 3.1.0 release, don't sweat it. If you want to see if its
really leaking, do what we do, which is to put it into a loop where it just
parses diffferent stuff over and over and watch the memory usage using
system monitoring tools (performance monitor on NT.)
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
Steve Chuang <[EMAIL PROTECTED]> on 03/23/2000 11:52:18 AM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: Robert Asis <[EMAIL PROTECTED]>, Alex Matevossian
<[EMAIL PROTECTED]>
Subject: memory leaks
To whom it may concern,
I'm experiencing some memory leaks. Here are all the details that I can
provide.
* Just by calling XMLPlatformUtils::Initialize() and doing absolutely
no parsing, I'm getting memory leaks when my test program terminates.
* I have attached a text file which contains contents that I copied
and pasted from the MSVC++ debug window.
* I stepped into the XMLPlatformUtils::Initialize() function, and
noticed that it calls the new operator there and some of the functions that
it calls. I searched all over the place and couldn't find any
uninitialization/cleanup code that deletes those pointers.
Here's some information you'll need according to the feedback procedures...
* Version of Xerces-C: 1.1.0
* OS platform: NT4 + SP4
* Compiler/version: MSVC++ 6.0
Thanks in advance for your help.
Regards,
Steve Chuang
IPNet Solutions, Inc.
<<leak.txt>>
(See attached file: leak.txt)
leak.txt
Description: Text - character set unknown
