Please check the following URL for ideas to improve the situation. http://xml.apache.org/fop/faq.html#OutOfMemoryException
On 15.04.2003 12:30:17 Daniel Tschan wrote: > We develop a client application which realizes printing through PDF > rendering. Since memory on the clients is limited and the users can > print hundreds of pages, the memory complexity of the PDF renderer must > not depend on the number of pages printed. But up to the latest FOP > release 0.20.4 exactly this is the case, if you use a single page > sequence. FOP runs out of memory after 10-40 pages. The page sequences > cannot be splitted without degrading the quality of the printing. Now > I've seen the following point on the changes page on the website: > Implemented on-the-fly stream output (less buffering leads to decreased > memory usage and increased speed) This only works as long as pages can be fully resolved. As soon as you have a "page x of y" on each page the first page can only be output when the last page is known. Changing that to "page x" only can help solve this problem. Other references play into this as well. > Does this solve this problem? In which version is it implemented? I tried > 0.20.5rc2. The situation is much better there, but not yet solved. The redesign contains some code that allows temporary serialization of pages until they are ready to be finalized. This will slow down the process but reduce memory usage. The problem is that a release from the redesign will still take a while so you're stuck with the above techniques to reduce memory usage until we have the redesign ready to take over. I hope that helps a bit. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
