2009/9/21 Remi Thomas <[email protected]>:
>
>>
>> It will be better if some of the core tesseract team just find and fix the
>> memory leak problems.
>
> There is no core team, the team it's you (I mean the community).
>
I haven't looked very deeply, but I've found two possible sources of
memory leaks so far:
Index: imgs.cpp
===================================================================
--- imgs.cpp (revision 319)
+++ imgs.cpp (working copy)
@@ -644,7 +644,7 @@
//put in destination
dest->put_line (xdest, ydest, destext, ©line, 0);
}
- delete linesums;
+ delete[] linesums;
}
@@ -785,7 +785,7 @@
//put in destination
dest->put_line (xdest, ydest, destext, ©line, 0);
}
- delete linesums;
+ delete[] linesums;
}
Could the OP test this and see if it fixes te problem?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
