We're compiling Tesseract using Visual Studio 2010, statically linking in Tesseract. We're seeing numerous memory leaks from the Tesseract code, and that's from simply calling init(no recognition, nothing else). There seems to be many objects of type Dawg allocated but never deallocated. Is this a known problem with the Tesseract codebase or are we perhaps doing something wrong? We see the memory leaks whether we call end() or not. We've noticed that many developers seem to prefer using Tesseract via command line rather than integrated into their codebase. Perhaps the memory leaks are a big driver for using Tesseract in this manner? Is the Tesseract codebase known to be riddled with memory leaks? Note that we've pulled down the latest code/V3.04.
-- 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 https://groups.google.com/group/tesseract-ocr. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/0e5b5907-833f-4309-88c1-38524483e502%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
