CraigBo wrote:
> I see that this fix has been applied to version 2.1.5. Is that version still
> on track to be released this month? (February 2009.)
Either it will be ready on Friday, or one week later.
--
This answer is provided by 1T3XT BVBA
http://www.1t3xt.com/ - http://www.1t3xt.info
I see that this fix has been applied to version 2.1.5. Is that version still
on track to be released this month? (February 2009.)
Craig
I've added Deflater.end() just in case the GC is slow to call finalize().
You can get it from the SVN.
Paulo
--
View this message in context:
http://www
.net
>> Subject: Re: [iText-questions] iText memory issue
>>
>>
>> Hi,
>> following on from my mail on the 23/12, we've built a version
>> a iText which
>> explicitly calls on the end() method on the Deflater object in the
>> com.lowagie.text.pdf
http://itext.svn.sourceforge.net/viewvc/itext?view=rev&revision=3632
Paulo
> -Original Message-
> From: Mallin, Eoin [mailto:emal...@revenue.ie]
> Sent: Monday, January 05, 2009 12:18 PM
> To: itext-questions@lists.sourceforge.net
> Subject: Re: [iText-questions]
Hi,
following on from my mail on the 23/12, we've built a version a iText which
explicitly calls on the end() method on the Deflater object in the
com.lowagie.text.pdf.PdfStream class. This has successfully resolved our
memory issue on Solaris 9. The Sun Bug ID that describes this issue is
4797189
> Subject: [iText-questions] iText memory issue
>
>
> Hi,
> first of all thanks for you great product. I've used it in a number
> applications to date.
>
> Recently we've come across an issue whereby our application
> was exhausting
> all native memory when
Hi,
first of all thanks for you great product. I've used it in a number
applications to date.
Recently we've come across an issue whereby our application was exhausting
all native memory when using iText. We're running the application on Solaris
9 and our Java memory settings are -Xmx2048m -Xms 2
