I gave it a try and it works great now, thank you for the fix!
Best regards,
Florian
- Original Message -
From: "Alberto Massari" <[EMAIL PROTECTED]>
To:
Sent: Thursday, January 06, 2005 2:06 PM
Subject: Re: Problem with SAX2XMLReader Memory Usage
Hi Florian,
a few days
Hi Florian,
a few days ago I committed a change that should fix the problem: can you
get the latest sources and try your testcase?
Thanks,
Alberto
At 13.18 06/01/2005 +0100, Florian Brugger wrote:
Regarding the SAX2Count memory usage problem:
Try using the following program to generate testfiles
Regarding the SAX2Count memory usage problem:
Try using the following program to generate testfiles:
#include
#define WITH_ATTRIBUTES
#define ELEM_COUNT 300
int main() {
FILE *fp;
if(!(fp=fopen("test.xml","wt")))
return -1;
fprintf(fp,"\n\n");
for(int i=0;i
#ifd
appreciate any advice on how to keep memory usage at a constant
level using a Xerces SAX parser as my application is expected to handle
arbitrarily large XML files.
Thank you,
Florian Brugger
-
To unsubscribe, e-mail: [EMAIL PROTECTED
consumption.
I would appreciate any advice on how to keep memory usage at a constant level
using a Xerces SAX parser as my application is expected to handle arbitrarily
large XML files.
Thank you,
Florian Brugger
-
To
at the very beginning. But there is
no point when I could call Terminate that would release the memory
because it can happen that all the time at least one thread can be
running so Terminate never will be the last one.
My question is: will in such situation grow the memory usage?
To understand
can happen that all the time at least one thread can be
running so Terminate never will be the last one.
My question is: will in such situation grow the memory usage?
To understand it better, the equivalent question would it be: if you
allocate, use and deallocate one Xerces document after
On Tue, 21 Aug 2001 09:54:41 -0400, Mark Northcott wrote:
>I thought that SAX avoided this type of memory consumption since it is
>event driven and simply notifies my custom ContentHandler as each type
>of XML tag is encountered.
It is. Replace your handler with an empty one, and measure mem u
I have tried using the latest nightly build, however I am still
experiencing the same problem. I think what I am looking for most is a
clarification as to how the SAX parser is working.
I expect the memory usage to fluctuate as the document is parsed such
that memory gets allocated when an
imply notifies my custom ContentHandler as each type
> of XML tag is encountered. Is there something I am missing here?
> Should SAX2XMLReader really be using this much memory? For example,
> while parsing an ~45M XML document, the memory usage rose to ~14M...
> this is not good because
parsing an ~45M XML document, the memory usage rose to ~14M...
this is not good because the program is expected to possibly handle
documents that are several hundred megs large.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Ehmm, Jeremy, you're creating a new XmlErrorReporter() in every iteration;
maybe you should try deleting that?
> -Original Message-
> From: Jeremy Ford [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 16:58 PM
> To: [EMAIL PROTECTED]
> Subject: memory u
> approximately 1000 times in 1 minute. After letting it run for several
> hours (10+), it now takes the parser over 3 minutes to parse the file.
> Also, using the task manager, I noticed that memory usage peaks at 190,000 K
> while parsing the file over the 3 minute period.
>
>
it run for several
hours (10+), it now takes the parser over 3 minutes to parse the file.
Also, using the task manager, I noticed that memory usage peaks at 190,000 K
while parsing the file over the 3 minute period.
My assumptions:
When parsing over a 3k file, memory should increase to some small fin
I believe that I resolved this problem. The DTD that I use has multiple
ATTLIST entries for each ELEMENT. This is a documented leak reported by :
Erik Rydgren
Mandarinen Systems AB, Sweden
Having just one ATTLIST for each attribute per ELEMENT seems to eliminate
the leak.
Sean Radcliffe wro
I am using xerces 1.4 with Win32. I am using the existing downloadable
binaries. When I parse multiple times in the same process, memory is
not relieved after each parse. As a test, I took the sample VC6
project DOMPrint (DOMPrint.cpp), and simply looped the code between the
parser creation an
ortal, Inc
[EMAIL PROTECTED]
-Original Message-
From: Zhang, Min [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 1:34 PM
To: [EMAIL PROTECTED]
Subject: memory usage of XML document
Hi,
How do I know the memory size of parsed XML document?
For example,
DOMParser parser;
pa
Hi,
How do I know the memory size of parsed XML document?
For example,
DOMParser parser;
parser.parse(xmlFile);
DOM_Document doc=parser.getDocument();
doc is just a referrencing object. How do I know the exact memory size of
the underlying XML document.
Thanks for your help!
min
--
18 matches
Mail list logo
