Created attachment 29607 [details] FO file illustrating the issue The page overflow recovery mechanism consists in pushing the overflowing content to the next page in the hope that it will be bigger and able to accommodate the content. When the IPD of the next page changes, the page breaking algorithm returns early and AbstractBreaker (doLayout method) splits the content and re-lays out what follows the page break, according to the new IPD. Those two mechanisms are in conflict when the overflow occurs at the first legal break, leading to no too short node and no feasible break. AbstractBreaker is then asked to split before the content, which it is not designed for. When the flow IPD changes the overflow mechanism must be disabled, since anyway the line breaking has to be re-done according to the new IPD.
Fixed in rev. 1411306: http://svn.apache.org/viewvc?rev=1411306&view=rev