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
Floating point exception on certain images when parameter tosp_old_to_method is set (some languages like Hindi set it by default) #3483
Comments
Maybe Update 2021-07-02: It is 0.0. |
The problem only occurs when the parameter It is possible to add Is that parameter needed at all, or could it always be forced to 0? |
@MerlijnWajer, as you process a huge amount of image (as far as I know also with Indic languages), I'd expect that this issue will also affect you as soon as you use Older code does not use FP exceptions, but silently shows undefined behaviour. |
Signed-off-by: Stefan Weil <sw@weilnetz.de>
I now fixed the crash in Git master, but would like to keep this issue open until it is clear how we proceed with |
Thanks for the fix, I confirm it's working now for my example image. However, I've found other images that, when transcribed with
I've reported it here in case it's related to the original report, but I can open a different issue if it's not. |
In that new case, the |
Rewriting the code avoids FP operations (so makes it potentially faster) and fixes the division by 0. Signed-off-by: Stefan Weil <sw@weilnetz.de>
I fixed that new division by 0 in commit 158c845. |
Thanks for the heads up. I'll pull the latest code, and if I run into problems like these I'll be sure to file an issue. |
The two floating point exceptions were fixed by @stweil. |
I opened a new related issue: #3614 |
Environment
Current Behavior:
-l hin
(I'm using the tessdata_fast version of the language files)Tesseract will die due to a floating point exception (division by zero?)
Expected Behavior:
I'd expect tesseract to transcribe the image without errors, instead of dying with a SIGFPE.
Suggested Fix:
Not really a suggested fix, but gdb shows where the error is happening:
The text was updated successfully, but these errors were encountered: