As it turns out, I found that I wasn't calling delete after I used DOMString.transcode() - which I was calling all over the place.
A good lesson. Jim Pearson -----Original Message----- From: Andy Clark [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 01, 2000 9:18 PM To: [EMAIL PROTECTED] Subject: Re: The DOM parser and memory management? (NEWBIE) James Pearson wrote: > I've noticed that memory usage climbs as I keep parsing new input files. I > had assumed that > Xerces would auto-magically handle the memory behind the scenes, but now I > wonder if I > have to "delete" the DOM_Document after I'm finished with it and before I > parse a new file. > (Of course my memory leaks could just be my lousy coding... nah.) Please pardon a Java guy for butting in here... I remember Andy Heninger doing a lot of work on the DOM implementation to make sure that it didn't leak memory. But... if you're not deleting the DOM_Document object then you *will* definitely leak. -- Andy Clark * IBM, JTC - Silicon Valley * [EMAIL PROTECTED]
