Yes, There is memory leak in tesseract and also some problems to reset the "state engine", this mean when you give the same file twice you don't get the same results. The only workaround is to use it in command line, this mean you create a new process for each document, Windows do the cleanup for you when the process exit.
Rémi On Jan 14, 7:26 pm, Jesse <[email protected]> wrote: > I have been searching for awhile for a semi decent OCR software that > has a .NET interface and was very happy to find tesseract (as well as > tessnet2) however I have implemented it and I have noticed an drastic > increased in memory usage after I read about 100 or so images. I have > been searching throughout the discussions and found that I was not > alone. I was wondering if anyone could tell me whether or not this is > tessnet2 error or if this is a tesseract error. And of course a way to > fix it, if possible. > > I was originally using MODI (M$ Office Document Imaging) to do my OCR > but the text reading was terrible and it just randomly crashed at odd > intervals causing the file it was reading at the time to lock up and > thus my program could not overwrite the file for the next pass. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en -~----------~----~----~----~------~----~------~--~---
