Corrupt JPEG data: Premature end of data segment about pdf2image HOT 14 OPEN

Do you have a PDF I could use to reproduce the error on my side?

from pdf2image.

Closing for inactivity.

from pdf2image.

I have document for the same. However I cannot share the document. If you can suggest then I can send you logs. Basically this error comes when pdftoppm is spawned and it waits for process to complete. However it waits infinitely till OK button is pressed on error popup. I am attaching Before and After pdf
POPUP Error

After POPUP Error Ok pressed

from pdf2image.

Hmm ok. I'll bring this up with the poppler team, maybe there is an envvar that can be set to prevent these.

from pdf2image.

thanks. just for information, I am using poppler for windows

from pdf2image.

Good news: Found the cause
Bad news: It's not overridable without recompiling libjpeg

https://github.com/libjpeg-turbo/libjpeg-turbo/blob/master/jerror.c#L104

I think I might just compile poppler on my side and distribute that instead of the alivate one.

from pdf2image.

In my current work, I've been using the pdf2image just to get the image object of the first page of the pdf. This is how I've been using it -> convert_from_path(filePathName, dpi=400, first_page=1, last_page=1, fmt='jpg')[0]
Now, the issue in my case is that it generates a similar JPEG Error but the message is different

I've checked the pdf file and there doesn't seem to be any issue with the file.
So, while this issue of windows dialog boxes for Error is still under work. Is there any way for us to just suppress the dialog box from our python script and continue with remaining tasks.

from pdf2image.

If there is, I haven't found it. It's packed in the library and there is no env var to deactivate it.

On the other hand, I will have more time to spare on this project shortly so I will probably be able to rebuild said library.

from pdf2image.

Not an issue. For the time being, I Just wrote a pywinauto script which runs concurrently and closes any such JPEG error window it finds.

from pdf2image.

is there any alternate option to avoid this?

from pdf2image.

Are you still experiencing this issue? It should have been fixed by #195

from pdf2image.

Are you still experiencing this issue? It should have been fixed by #195

I still get the "Corrupt JPEG data: Premature end of data segment" occasionally. I am using pdf2image Version: 1.16.0.

Has this PR been incorporated in the latest distributed version on PyPi?

from pdf2image.

Yes it should be in the latest version available on PyPI. If you are still experiencing this issue then it was not fixed.

Unfortunately I cannot reproduce the issue so there is not much that I can do.

from pdf2image.

Actually updating poppler (basically using the version you've suggested in the READ.ME) worked. The issue is gone.

from pdf2image.