It is well known that Tesseract has multiple memory leaks so I think you can periodically unload the managed wrapper .NET assembly and load again. To do so you could load it in a separate application domain and unload the entire domain and re-create it periodically (e.g. when the memory consumption reaches some threshold).
See more about application domains, loading and unloading assemblies at runtuime here: http://msdn.microsoft.com/en-us/library/ms173101.aspx Regards, Svetlin Nakov Managing Partner Consulting and Information Technology Agency http://www.citagency.eu -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of nicdnepr Sent: Friday, September 18, 2009 3:06 PM To: tesseract-ocr Subject: memory problem hi i use Tessnet2 a .NET 2.0 Open Source OCR assembly using Tesseract engine from article http://www.pixel-technology.com/freeware/tessnet2/ after 1000 persed images i have 500 MB memory used in program. how can i resolve this? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
