In case anyone is confused when they read the draft.mode work-around in the Debian bug, I'll try to explain here.
The Debian bug reporter's FO document did not originally contain images. When FOP produces a draft output (draft.mode=yes), it inserts a background image that says "DRAFT" or something like it on each page, as a sort of watermark. This image insertion causes his crash.
My input documents do contain images (screenshots of our software), so disabling draft mode (and removing the background image) doesn't help me. They still contain images, and FOP crashes.
In case anyone is confused when they read the draft.mode work-around in the Debian bug, I'll try to explain here.
The Debian bug reporter's FO document did not originally contain images. When FOP produces a draft output (draft.mode=yes), it inserts a background image that says "DRAFT" or something like it on each page, as a sort of watermark. This image insertion causes his crash.
My input documents do contain images (screenshots of our software), so disabling draft mode (and removing the background image) doesn't help me. They still contain images, and FOP crashes.