I downloaded the latest code changes and compiled it with tessnet2 and the memory leak still appears to be there. If someone gets a different result please post the tessnet2.dll.
On Jan 15, 11:03 am, "Ray Smith" <[email protected]> wrote: > Can you test against the latest code in svn? I think the memory leaks are > fixed in there, but I am not sure. (Confused as to what was fixed when.)Let > me know what you find, so I can try to incorporate more fixes from 3.00 if > necessary. > Ray. > > On Wed, Jan 14, 2009 at 10:26 AM, 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 -~----------~----~----~----~------~----~------~--~---
