You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2002/09/03 17:30:44 UTC
DO NOT REPLY [Bug 12262] -
Lacking detection of endless loops
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12262>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12262
Lacking detection of endless loops
------- Additional Comments From raultman@fcci-group.com 2002-09-03 15:30 -------
This bug has some relationships to bug #8778 which I've offered some commentary
on. The same problem may be occurring in each case- a FO document is being
generated such that some single element is spilling over the pagebreak, causing
FOP to put it on a new page, where it then spills over the pagebreak...ad
nauseum. The comments in bug #8778 were for FOP 0.20.3, but the bug hasn't
been assigned or resolved, so it's probably valid in FOP 0.20.4. Any attempt
at addressing this issue of the infinite looping should address both the cases
mentioned here and in bug #8778 as well.
Possibly a simple solution is to track whether or not FOP tries to position the
same object on a new page more than twice? The moment an object is placed on a
fresh, new page and cannot fit, there is no need to continue- no future pages
are going to fit it, either.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org