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] -----Original Message----- From: Stanimir Stamenkov [mailto:[EMAIL PROTECTED] Sent: Tuesday, 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 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 (I recall this was improved in Java 5). I would ask what JRE is used? A "Spurious OutOfMemoryError exceptions" [1] issue was fixed recently in the Sun's Java 1.4.2_13 [1] and 1.5.0_10 [2]. [1] Bug ID: 4855795 <http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4855795> [2] Changes in 1.4.2_13 <http://java.sun.com/j2se/1.4.2/ReleaseNotes.html#142_13> [3] Changes in 1.5.0_10 <http://java.sun.com/j2se/1.5.0/ReleaseNotes.html#150_10> -- Stanimir -- Stanimir --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
