Issue Details (XML | Word | Printable)

Key: CONF-1728
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Dave Loeng [Atlassian]
Votes: 9
Watchers: 10
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

PDF Export error - No meaningful layout in block after many attempts

Created: 26/Aug/04 07:14 PM   Updated: 24/Mar/08 10:37 PM
Component/s: PDF Generation
Affects Version/s: None
Fix Version/s: 2.6.0

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference
 

Participants: Agnes Ro [Atlassian], Dave Loeng [Atlassian], Matt Ryall [Atlassian], Matthew Jensen [Atlassian], Michael Trezzi and Olli Kallioinen
Since last comment: 36 weeks ago
Internal Complexity: 3
Resolution Date: 24/Mar/08 10:36 PM
Support reference count: 54
Internal Value: 8
Labels:


 Description  « Hide
Stack trace:

SEVERE: Error while generating PDF!
org.apache.fop.apps.FOPException: null:110:1982 No meaningful layout in
block after many attempts. Infinite loop is assumed. Processing
halted.
at org.apache.fop.fo.flow.Block.layout(Block.java:140)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at org.apache.fop.fo.flow.Block.layout(Block.java:257)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)
at
org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:110)
at
org.apache.fop.fo.pagination.PageSequence.makePage(PageSequence.java:400



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Dave Loeng [Atlassian] added a comment - 26/Aug/04 07:17 PM
This error means you have a page that contains a table or image too large to fit on the PDF page being exported to.

If you are exporting a page you will have to narrow down which page it is by doing a binary search. That is, if your space had 200 pages, attempt to export the space with only the first 100 pages and then again on the 100 pages that produced an error and so forth until you narrow it down.

Removing or resizing the table should generally fix the problem.

Closing this issue with this workaround.


Dave Loeng [Atlassian] added a comment - 03/Jan/06 06:10 PM
It appears that this problem goes away so long as the first image that appears is of reasonable size.

Hence another workaround is to:

  • rearrange the order of your image a bit by shifting one image of reasonable size to be first on the list
  • alternatively, if they are all large, simply reduce the size of the first.

Agnes Ro [Atlassian] added a comment - 09/Jan/07 07:14 PM
You could also try customizing pdf's with a bigger width http://confluence.atlassian.com/display/DOC/Customise+Adobe+PDF+Exports, although it would affect all pdf exports.

Michael Trezzi added a comment - 27/Feb/07 06:06 AM
I think if a page contains an image that is too large, it should either be able to resize it to fit on page or cut it in pieces. But it should not end with error. For a user, that has no idea what is going on, this is unacceptable.

Matthew Jensen [Atlassian] added a comment - 28/Feb/07 12:55 AM
This issue occurs only if the image is too high for the page. FOP uses the width of the image to calculate the scaling and if its wide enough, you wont see this issue.

Matthew Jensen [Atlassian] added a comment - 28/Feb/07 12:56 AM
This issue similar to what happens with Apache Forrest (which uses FOP internally).

See:
http://issues.apache.org/jira/browse/FOR-413


Olli Kallioinen added a comment - 25/May/07 10:33 AM
Adding a smaller image before the large image did not work as a workaround for me. I tried setting a smaller height parameter for the image so I would not have to scale the image, but that didn't help either.

Adding "align=center" parameter to the image worked however.


Matt Ryall [Atlassian] added a comment - 04/Oct/07 01:53 AM
Agree we should be able to handle this error more gracefully. A warning to the user which includes the page affected would be suitable.

Dave Loeng [Atlassian] added a comment - 24/Mar/08 10:36 PM
Fixed in 2.6.0.

We have verified that the images provided by customers that previously caused errors, no longer do when performing PDF exports in the latest 2.7.3.