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
ocrd-tesserocr-segment: segmentation fault #182
Comments
Tried to reproduce this bug with plain tesseract:
but I don't know if those options are equivalent to the above. |
I'll have approx. 1500 "core.12345" files of 62k TIFs = 2.4 % (!). Dear @stweil, could you prioritize this issue? |
I must try to reproduce it in my environment. That would be easier if the problem would also occur with plain |
@jbarth-ubhd The mechanism used for ocrd_tesserocr's
@stweil, the underlying cause is a bug in the iterator (state) functions – but I have no time to work on Tesseract, and my fix has become more difficult to work on after the recent upstream changes. |
Please try this patch for the Tesseract code:
|
@jbarth-ubhd, the latest tesseract git main includes the patch which fixes the segmentation fault. Maybe you want to try it and can report whether it produces usable results for the examples which crashed with the old code. I cannot test it myself without the model |
Thanks. I could run your workflow after an update to latest tesseract and had no problems. |
@jbarth-ubhd The fix @stweil mentioned is also part of the newest ocrd_all release, so please update your docker/singularity image. |
@jbarth-ubhd, can we close this issue? |
yes. |
And with this image:
https://digi.ub.uni-heidelberg.de/diglitData/v/justinian1627bd2_-_1281.tif
and ocrd.sif (singularity container) created from docker ocrd_all at Nov 9 10:13 2021 & at Jan 17 15:11 2022 [UPDATE]
and this workflow:
I'll get a
segmentation fault
The text was updated successfully, but these errors were encountered: