That might work but sounds dangerous. I just took a more careful look at what pixCreate() does, and by default it allocates memory for you. The implication being that you are supposed to copy your image data into that location.
In any case, you should definitely check your routine for memory leaks. Loop it say 100 times and watch your memory usage (and GDI handle usage). Something like Sysinternals Process Explorer can be helpful here. Or possibly look into Visual Leak Detector [2]. [1] http://technet.microsoft.com/en-us/sysinternals/bb896653 [2] http://vld.codeplex.com/documentation -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en
