We are building the Tesseract code with Visual Studio and we've found where some (apparently) compiler optimization bugs are affecting us - definitely with VS2013 Community, but also perhaps with VS2008. Some of your details (x86 but not X64) sound similar - but this is a very "conditional" problem depending on image data, code and sometimes threading.
I solved it for us by adding some #pragma statements to disable optimization for the problematic function. I reported details in my latest notes for https://code.google.com/p/tesseract-ocr/issues/detail?id=1496 If you're building with VS then my changes are worth a try. Let us know what you find! -= Rich Taylor On Sunday, August 9, 2015 at 6:19:23 AM UTC-4, Kenz Kenza wrote: > > Hello; > I am using VB.NET and Tesseract OCR (using CUBE_COMBINED) to extract text > from a 300ppp jpeg Images. I am testing almost 45 Image. When I use x86 as > target It works untill the Image number 7 and stops with an SEHException. > It does not complet.. I tried to change the platform to x64 CPU and It > worked with no Issue. > The costumer of my project has only x86 platform and the project should > work on his computer.. So any solution for that?? I am really suck.. > -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tesseract-ocr. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/78f836b8-cdbc-49ea-8936-655bfcab2ceb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
