DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40615>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40615


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




------- Additional Comments From [EMAIL PROTECTED]  2006-09-27 11:30 -------
Please study http://xmlgraphics.apache.org/fop/0.92/running.html#memory and
search the mailing list archives of the fop-users mailing list for additional
suggestions on how to cope with memory problems:
for example:
http://www.nabble.com/forum/Search.jtp?forum=353&local=y&query=outofmemory

In case you have many images in your file, you might want to try the latest FOP
Trunk (from the Subversion repository) which has a memory fix for the image 
cache.

If your document is mostly an overly large but simple tabular report (as I
assume it is) you might have to consider having chosen the wrong tool. There are
tools (reporting engines) better suited for handling such tabular reports. Maybe
one day FOP can handle such documents without special precautions, but today it
can only handle them if you're able to give enough memory and manually split the
document in multiple page-sequences (which brings the memory consumption down).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to