-
-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heroku tesseract build pack support? #123
Comments
Hi, @ansonl First, have you tried I personally recommend using Docker for your heroku application because it's more flexible and easy to handle. I'm gonna try buildpack when I have a time. |
Unfortunately I wasn't able to get the libtesseract-dev buildpack working. This also confirmed what seems to be a memory leak issue in the Tesseract BaseAPI.End() function. When calling the End() function and letting client go out of scope, memory usage decreases slightly, but still takes up a couple megabytes of memory for each client struct created. This can be seen by running the below test program:
For some reason, after the clients are closed and the tesseract BaseAPI End() method should be called, memory usage will remain elevated. I have tried calling the Go garbage collector functions and it seems to make no difference. The only way I have found to release the memory is to exit the program. I looked through the .cpp file and have not seen any bugs, so this may be a tesseract library issue. |
@ansonl |
Is there a working configuration to get this working with one of the Heroku tesseract buildpacks such as https://github.com/Dkevs/heroku-buildpack-tesseract?
When compiling go app, Heroku gives error
I've tried setting CGO_CFLAGS in heroku like
heroku config:set CGO_CFLAGS='-I ${build_dir}/tesseract/../'
to no avail.I see the example heroku project uses docker and installs libtesseract-dev. Wondering if gosseract is only tested with docker and if you can recommend a buildpack for libtesseract-dev.
The text was updated successfully, but these errors were encountered: