t: Re: Memory leak in DomParser
/Avihai Marchiano/:
> I test it with JProbe and it seems that the diagnostic, which describe
> in the following post is the problem:
>
>
http://mail-archives.apache.org/mod_mbox/xerces-j-users/200212.mbox/%3c2
[EMAIL PROTECTED]
Have you tried the prop
/Avihai Marchiano/:
I test it with JProbe and it seems that the diagnostic, which describe
in the following post is the problem:
http://mail-archives.apache.org/mod_mbox/xerces-j-users/200212.mbox/[EMAIL
PROTECTED]
Have you tried the proposed changes from the referenced message?
From the r
, January 09, 2007 1:26 PM
To: j-users@xerces.apache.org
Subject: Re: Memory leak in DomParser
>> I check it also in 2.9, and the problem still exists.
>
> It'd be easier to diagnose if we had:
> a) a sample of the input to the parser
> b) the stacktrace generated when the p
>> I check it also in 2.9, and the problem still exists.
>
> It'd be easier to diagnose if we had:
> a) a sample of the input to the parser
> b) the stacktrace generated when the program fails
As far as I know there's no stack trace available to OutOfMemory errors with
the Sun's Java 1.3/1.4
It'd be easier to diagnose if we had:
a) a sample of the input to the parser
b) the stacktrace generated when the program fails
Chris
-Original Message-
>From: Avihai Marchiano <[EMAIL PROTECTED]>
>Sent: Jan 8, 2007 4:04 PM
>To: j-users@xerces.apache.org
>Subj
I check it also in 2.9, and the problem still exists.
-Original Message-
From: Michael Glavassevich [mailto:[EMAIL PROTECTED]
Sent: Monday, January 08, 2007 10:50 PM
To: j-users@xerces.apache.org
Subject: Re: Memory leak in DomParser
Is there something preventing you from moving to a
Is there something preventing you from moving to a more recent release
(like 2.9)? Xerces-J 2.2 is over four years old now. We've fixed hundreds
of bugs since then. Several of the fixes were for memory leaks.
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E
