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=44358>. 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=44358 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-07 03:23 ------- (In reply to comment #5) > Thanks for the response. > > We are using preserve-whitespace property in our stylesheets. That could be > causing the infinite loop. We don't want to go to production with Trunk code. > But, if you could please point out to the classes from the Trunk code that > fixed > this problem, I can get those and include them in the 0.94 jar and run our > stylesheets. Let us know. Edit the src/java/org/apache/fop/layoutmgr/table/TableContentLayoutManager.java file and delete lines 145 and 166, which correspond to the following lines of code: ElementListUtils.removeLegalBreaks(this.headerList); ElementListUtils.removeLegalBreaks(this.footerList); They are causing the infinite loop. Removing them is totally safe and won't affect the quality of the layout. Vincent > > (In reply to comment #4) > > 1) There was a bug in the Layout code that meant an infinite loop could be > > entered for certain FO. IIRC, preserve-whitespace property had something to > > do > > with it. This has been fixed in the Trunk code. > > 2) long page-sequences are a problem for FOP because FOP uses a total-fit > > algorithm to layout the FO. This has the advantage of achieving more > > elegant > > layout but the disadvantage of requiring the whole page-sequence to be kept > > in > > memory and it is only released when the whole page-sequence has been > > finished. > > I think forward references via fo:page-number-cititation can also cause FOP > > to > > hang onto more objects in memory until the forward reference is resolved. -- 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.