<br><font size=2 face="sans-serif">I have run into the memory problem parsing an 800k file.</font>
<br>
<br><font size=2 face="sans-serif">I have been to the jdom.org site and only seem to have two options, the beta8 with the problems or the very latest cvs code with severe sounding warnings on it.</font>
<br>
<br><font size=2 face="sans-serif">It there a milestone release available in binary anywhere.<br>
<br>
/Phill<br>
IS Dept, Software Engineer.<br>
phill_perryman@mitel.com<br>
http://www.mitel.com<br>
Tel: +44 1291 436023</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Alex Rosen" <arosen@novell.com></b></font>
<br><font size=1 face="sans-serif">Sent by: jdom-interest-admin@jdom.org</font>
<p><font size=1 face="sans-serif">27/02/2003 15:14</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To: <laurent.bihanic@atosorigin.com>, <malachi@tremerechantry.com></font>
<br><font size=1 face="sans-serif"> cc: <jdom-interest@jdom.org></font>
<br><font size=1 face="sans-serif"> Subject: Re: [jdom-interest] RE: Memory and Speed problems with SAXBuilder</font></table>
<br>
<br>
<br><font size=2 face="Courier New">The beta 8 problem was not limited to JDK 1.4.1. I know it happened on<br>
JDK 1.2.2 also, and I thought it happened on JDK 1.4.0 as well, but I'm<br>
not positive.<br>
<br>
Alex<br>
<br>
>>> Laurent Bihanic <laurent.bihanic@atosorigin.com> 2/27/2003 4:47:27<br>
AM >>><br>
<br>
Hi,<br>
<br>
Malachi de AElfweald wrote:<br>
> Worst performer was SAXBuilder (which I originally used because we<br>
were <br>
> building from<br>
> an InputStream). Also, SAXBuilder was the ONLY one that required the<br>
<br>
> huge amount of<br>
> heap space.<br>
<br>
You are probably using JDOM beta8 with JDK 1.4.1. These two are<br>
incompatible <br>
due to the memory leak bug in StringBuffer introduced in JDK 1.4.1.<br>
For more information, please see <br>
http://developer.java.sun.com/developer/bugParade/bugs/4724129.html <br>
<br>
Sun does not plan to fix this bug until JDK 1.5 (Tiger).<br>
<br>
To fix this problem, you have 2 solutions:<br>
1. Stick to JDOM beta8 but downgrade to JDK 1.4.0 or 1.3.1<br>
2. Stick to JDK 1.4.1 and upgrade to the latest JDOM which includes a<br>
<br>
workaround for the JDK bug.<br>
<br>
Laurent<br>
<br>
_______________________________________________<br>
To control your jdom-interest membership:<br>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com<br>
_______________________________________________<br>
To control your jdom-interest membership:<br>
http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com<br>
</font>
<br>
<br>