You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xerces.apache.org by mgerde - Mark Gerdes <mg...@acxiom.com> on 2000/03/29 23:59:17 UTC
RE: Participate - mem leaks
I am a novice C++ coder, novice Xerces 1.1.0 user and new to
the list as well. A triple newbie.
I also am getting memory leaks from VC6 and BoundsChecker (I am using
MFC) with the largest leak being from
DOMStringHandle *dsg = ::new DOMStringHandle[allocGroupSize];
I've looked back through the archives and have seen the subject
discussed in a fragmentary way but don't have a clear picture of
what I need to do to clean up this memory or if they are just
artifacts created by my BoundsChecker.
Would it be a good idea to do a quick FAQ regarding these memory
leaks? This seems to have come up quite a bit and a quick FAQ
might help cut down on ignorant newbies such as myself asking what
has probably already been explained more than once.
Thanks very much,
Mark Gerdes
-----Original Message-----
From: Paul Wilkerson [mailto:pwilkerson@quarium.com]
Sent: Wednesday, March 29, 2000 3:22 PM
To: xerces-dev@xml.apache.org
Subject: Participate
I would like to participate as a Beta tester of Xerces. I am already using
xerces and would like to give feedback. I am developing under windows NT
4.0, with DevStudio 6 SP3. I am using the SAX API primarily, in conjunction
with MFC. Curently DevStudio is reporting memory leaks. How cam I best help
to fix this problem.
Paul Wilkerson
Quarium, Inc.