[ 
https://issues.apache.org/jira/browse/PDFBOX-2596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281093#comment-14281093
 ] 

John Hewson commented on PDFBOX-2596:
-------------------------------------

I guess you didn't read the JavaDoc:
{code}
/**
 * This is the in-memory representation of the PDF document.  You need to call
 * close() on this object when you are done using it!!
 * <p>
 * This class implements the {@link Pageable} interface, but since PDFBox
 * version 1.3.0 you should be using the {@link PDPageable} adapter instead
 * (see <a 
href="https://issues.apache.org/jira/browse/PDFBOX-788";>PDFBOX-788</a>).
 *
 * @author <a href="mailto:b...@benlitchfield.com";>Ben Litchfield</a>
 * @version $Revision: 1.47 $
 */
public class PDDocument implements Pageable, Closeable
{code}

We also implement Closeable, which is about as clear as you can get.

> NullPointerException in RandomAccessFileInputStream
> ---------------------------------------------------
>
>                 Key: PDFBOX-2596
>                 URL: https://issues.apache.org/jira/browse/PDFBOX-2596
>             Project: PDFBox
>          Issue Type: Bug
>    Affects Versions: 1.8.8
>            Reporter: John Roche
>
> Line 94 contains a synchronized(file) that throws a NullPointerException 
> under some strange circumstances that I haven't been able to fully identify 
> yet.  I have downloaded the 1.8.8 source and the fix I used is simply to add 
> "&& file != null" to the previous if statement.
> I can reproduce this bug with live user data, but I haven't been able to with 
> test data yet.  It happens when I try to create a pdf with 36 pages that have 
> an image, some drawn coloured boxes and some text, on each page.  If I remove 
> some of the pages before I call save(File) it doesn't happen - depending on 
> which pages I remove it can be ok with up to 26 pages, or break with fewer.  
> Quite strange.  I suspect it's to do with the size of the data as opposed to 
> the number of pages.
> I will continue to investigate, since there seems to be some underlying 
> issue, but for now I guess the null protection should be ok to add?
> Thanks,
> John



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to