Memory leak

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run a lot of documents through python-tesseract, use GetUTF8Text

What is the expected output? What do you see instead?
Normal expected output (success or error)

double free or corruption is seen as follows:

Error in boxClipToRectangle: box outside rectangle
Error in pixScanForForeground: invalid box
*** Error in `/usr/bin/python': double free or corruption (!prev): 
0x0000000007ba4da0 ***
Fatal Python error: Aborted

Current thread 0x00007fcacaa0e740:
  File "/usr/local/lib/python2.7/dist-packages/python_tesseract-0.9-py2.7-linux-x86_64.egg/tesseract.py", line 10484 in GetUTF8Text

What version of the product are you using? On what operating system?
ubuntu 14.04 python 2.7.8 python-tesseract 0.8-19 tesseract 3.03 leptonica-1.70 
libgif 4.1.6(?) : libjpeg 8d : libpng 1.2.50 : libtiff 4.0.3 : zlib 1.2.8 : 
webp 0.4.0

Please provide any additional information below.
On a few different types of document extraction tasks, when putting python 
tesseract through long iterative lists of extraction, typically after seeing 
some errors (which normally don't cause a crash), a double free or corruption 
segfault occurs, killing python and any associated worker

Original issue reported on code.google.com by ch...@fiscalnote.com on 2 Oct 2014 at 8:02

[GoogleCodeExporter]

Can u identify the leak? Is it due to the wrapper or due to the tesseract 
itself?

Original comment by FreeT...@gmail.com on 3 Oct 2014 at 4:01

[GoogleCodeExporter]

I believe it's due to the wrapper but may be tesseract itself, How can I go 
about debugging this further?

Original comment by ch...@fiscalnote.com on 6 Oct 2014 at 4:38

[GoogleCodeExporter]

If you run the simple job again using c++ in tesseract and find no problems, 
then the wrapper is the root cause.

Original comment by FreeT...@gmail.com on 8 Oct 2014 at 2:57