-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] tesseract returns SIGFPE Signal #1062
Comments
I made a issue on the tesseract repo too, I guess its not really related to OCRmyPDF |
An option to ignore tesseract errors would be nice. So that the page with an error is just skipped instead of crashing OCRmyPDF |
I'm reluctant to add such an option because it could mask more serious issues than a one-time failure. I think it's reasonable for the program to ask for user intervention in this case, and an exception is a good way of doing that. One could write a plugin to suppress errors from the OCR engine if needed. |
just a side note
for page 42 but did not crash and just created a complete pdf. It also uses tesseract, I tried to dig a little into the code of gsccan2pdf, to find a difference in the way it executes tesseract, but gave up... (I guess they have a fallback to cuneiform/gocr, not totally sure) |
Describe the bug
tesseract returns SIGFPE Signal?
To Reproduce
I also tried without
--jobs
and with--force-ocr
Example file
This only happens with this test file, on 33 similar files it worked without problems.
test file is up for 30 days:
https://easyupload.io/as1sst
System
14.0.2
The text was updated successfully, but these errors were encountered: