tesseract: Unhandled exception in InteropRuntimeImplementer.TessApiSignaturesInstance on Windows Server 2019 with Tesseract 4/4.1

Hi Charles,

For couple of days I’m trying to find out why I’m getting the unhandled exeception when calling tesseract using your wrapper (a couple of months I compiled and created nuget from your branch 321-tesseract-4 or the current develop 4.1.0-beta1) on Windows Server 2019 in my application compiled using x86 platform.

On my developper Windows 10 machine I have no issue. On server the MVCPP 2015-2019 are installed for x86 and x64.

I can reproduce the problem using your console sample application (and targeting net 4.7.2 for example [<TargetFrameworks>net45;net472;netcoreapp3.0</TargetFrameworks>] and using Any CPU or x86 platform): Exception non gérée : System.Runtime.InteropServices.SEHException: Un composant externe a levé une exception. à InteropRuntimeImplementer.TessApiSignaturesInstance.TessApiSignaturesImplementation.BaseApiRecognize(HandleRef handle, HandleRef monitor) à Tesseract.Page.Recognize() à Tesseract.Page.GetText() à Tesseract.ConsoleDemo.Program.Main(String[] args) dans C:\Users\ak\OneDrive\Dev\GitHub\tesseract-samples\src\Tesseract.ConsoleDemo\Program.cs:ligne 24

Remote debugging shows the following error:

Do you have any ideas what is causing it?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 37 (14 by maintainers)

Commits related to this issue

Compiling without optimizations Disabling the optimization options when generating tesseract. with `-DAUTO_OPTIMIZE=OFF` [Issue 497](https://github.com/charlesw/tesseract/issues/497#issuecomment-5601... — committed to Soruk/tesseract by Soruk 5 years ago

Most upvoted comments

FYI I’ve just released a new version 4.1.1 with the dlls built with AVX support disabled which should resolve theses issues. Sorry for the delay and thanks again @Soruk for identifying and sorting out this issue 😃

charlesw on Nov 15, 2020

No, it is not necessary to build nuget. I updated the DLLs and references to it and make some changes in order to build package (with Visual Studio 2019 there is an option on contextual menu to generate package)

Soruk on Nov 3, 2020

Hi,

I resolved by building the wrapper (in my fork branch) and creating the corresponding nuget package that I store at our company’s repository.

Soruk on Nov 3, 2020

Hi,

I created the pull request 499 into your branch with updated tesseract and leptonica.

Soruk on Dec 2, 2019

Actually one other thing to check would be that the dependencies (libjpeg, etc) weren’t compiled with avx instructions enabled as that would obviously fail if that was the case. So to summarize:

Ensure tesseract, leptonica, and all dependencies are not compiled with avx instructions
Ensure tesseract does not generate / use any AVX instructions dynamically (1348)

BTW just to be clear are you running this on a VM? If so that may explain why some of the dynamic instruction checks appear to be failing as I’m pretty sure windows server 2019 support AVX2.

charlesw on Nov 30, 2019