Hi Hamed, I did some pretty large publications with lots of images. 1500 pages took 2GB memory, after I put some effort in memory optimization. The only FOP-related issue I found was image caching and that can be disabled. I'm quite sure I would have found a memory leak in FOP, especially one related to ordinary LayoutManagers. So either make your page-sequences shorter or give fop more memory.
Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de<http://www.geneon.de> Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de<http://www.irs-nbg.de> Willmy PrintMedia GmbH: www.willmy.de<http://www.willmy.de> Willmy Consult & Content GmbH: www.willmycc.de<http://www.willmycc.de> Von: Hamed Mohammed [mailto:[email protected]] Gesendet: Donnerstag, 9. September 2010 19:55 An: [email protected] Cc: Dominik Stadler; Craig Ringer Betreff: Re: Memory Leak issue -- FOP Hi, Attached word file includes snap shots of exeption and heap dump analysis. On Wed, Sep 8, 2010 at 7:10 PM, Craig Ringer <[email protected]<mailto:[email protected]>> wrote: On 9/09/2010 1:55 AM, Hamed Mohammed wrote: Hi, This the expection I get when I try to convert XSL:FO to PDF . Did you try to attach a screenshot or something? Put the exception text in a text file attachment (to protect it from email client word wrapping) or paste it here: http://pastebin.com/ ... and include the link it give you in your email. -- Craig Ringer Tech-related writing at http://soapyfrogs.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]> -- Thanks, Hamed Mohammed, Email: [email protected]<mailto:[email protected]>.
