Closed 0xbad1d3a5 closed 7 years ago
Yup, that's definitely the problem. Calling TessBaseAPI.getHOCRText(0)
instead allows you to stop and cancel the recognition.
Fixed, as well as fixing some code upstream: https://github.com/rmtheis/tess-two/pull/186
I think I know the cause here.
The GetUTF8Text() function in tesseract does not pass a monitor to Recognize, so recognition will never be canceled and will always block.