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=13079>. 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=13079 PDFXObject made a very bad FOPImage.close() call Summary: PDFXObject made a very bad FOPImage.close() call Product: Fop Version: all Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Two Threads access same global image and one of the thread kill the content before the other thread can load the image ! org.apache.fop.pdf.PDFXObject ... protected int output(OutputStream stream) throws IOException { .... // don't know if it's the good place (other objects can have references to it) fopimage.close(); ... >>>> This is the absolute wrong place to close the image! Please delete the line! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
