Hi,
On Wed, 20 Nov 2002, Bagepalli, Kiran wrote:
> Hi Gareth,
> Thanks for the clarification.
> Still have a few more things to clarify.
> 1. Is the problem relating to releasing attributes limited to ID
> attributes because thats what bugzilla says or this
> problem will occ
).
Thanks
Kiran
-Original Message-
From: Gareth Reakes [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 20, 2002 2:54 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Memory growth in DOM
Hi Kiran,
perhaps we are using different terminology here and confusing each
oth
On Tue, 19 Nov 2002, Bagepalli, Kiran wrote:
> Actually I tested with a file with repeating element and attribute values.
> DOM application monitored using DOMCount grew to almost three times the
> size. 20MB XML file took 75MB in memory.
> Am I missing something?
> Kiran
I dont think this is un
Hi Kiran,
perhaps we are using different terminology here and confusing each
other. I will attempt to explain my understanding.
i) Things like element and attribute names are stored in a memory block
and are acquired by calling getPooledString. These are strings managed by
the document a
On Tue, 19 Nov 2002, Bagepalli, Kiran wrote:
> Following up on the question, if the element data and attributes are string
> pooled, are they reference counted as well.
>
> Say I have a DOM Tree, two parts of a DOM tree use data from the string
> pool. If I release the first part, is the pool cle
PROTECTED]]
Sent: Tuesday, November 19, 2002 12:15 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Memory growth in DOM
Actually I tested with a file with repeating element and attribute values.
DOM application monitored using DOMCount grew to almost three times the
size. 20MB XML file took 75MB
]]
Sent: Tuesday, November 19, 2002 10:57 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Memory growth in DOM
Following up on the question, if the element data and attributes are string
pooled, are they reference counted as well.
Say I have a DOM Tree, two parts of a DOM tree use data from the s
-
From: Gareth Reakes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 19, 2002 12:45 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Memory growth in DOM
Hi,
> I had posted this question in the past with no reply. What kind of
> approach does xerces code employ when managing DOM dat
Hi,
> I had posted this question in the past with no reply. What kind of
> approach does xerces code employ when managing DOM data.
It allocates blocks of memory that are managed by the document. Some of
these are recycled.
> I believe the element/attribute values are in a string pool.
Ye
