I have an application that caches an object that contains a DOM_Document
object. The application doesn't rely on the cached document, it just
happens to be an attribute to this cached class. When the application
retrieves this object from the cache, it attempts to update the document
object (i.e
thanks for your help
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 01, 2001 3:48 PM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
"Christy, Rich" wrote:
> However, I do see several references to possib
getElementsByTagName(). Any ideas?
Thanks
Rich
-Original Message-
From: Alberto Massari [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 10:29 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
At 08:08 AM 10/31/2001 -0800, you wrote:
>"Christy, Ric
OK, I'll give that a try.
Thanks
-Original Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 31, 2001 10:09 AM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
"Christy, Rich" wrote:
> Actually purify was complaining of
application need to do is to delete
the
document if you are building the tree yourself. See
http://xml.apache.org/xerces-c/program.html#IDOMMemMgmt for more details.
Tinny
"Christy, Rich" wrote:
> Tinny,
>
> The code segment looks like this:
>
> const IDOM_Element*
&
//xml.apache.org/xerces-c/program.html#IDOMMemMgmt for more details.
Tinny
"Christy, Rich" wrote:
> Tinny,
>
> The code segment looks like this:
>
> const IDOM_Element*
> IDOMStreamer::findElement(const char* elementName, const IDOM_Element
> *parentElement) const
iginal Message-
From: Tinny Ng [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 4:01 PM
To: [EMAIL PROTECTED]
Subject: Re: delete[] problems with transcode
Christy,
Can you post more detail, e.g. how does IDOMStreamer::findElement call
transcode()?
Thanks!
Tinny
"Christy,
I trying to determine if this is a problem or not. But each time I call
getElementsByTagName(), it works its way down to
IDDeepNodeListImpl::getDeepNodeList() where memory is allocated to and
inserted into the node list pool. Purify claims a memory leak is occurring.
I cannot find any where in t
Searching the bug database, I found Bug 3052 documenting a problem with
getElementsByTagName() core dumping in a call IDDeepNodeListPool.cpp file
with multiple threads. I'm seeing the same problem using the 9/14 build on
Solaris. The database said this bug was a duplicate. Has it been fixed in