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/27 16:10:03 UTC

DO NOT REPLY [Bug 13079] New: - PDFXObject made a very bad FOPImage.close() call

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: fop-dev@xml.apache.org
        ReportedBy: pr@webapp.de


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: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org