You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jan 04 23:58
Hi, we have a light weight dockerized microservice that accepts image OCR scan requests using your library. On occasion, we see zombie tesseract processes lingering and taking up resources. Almost as if php exec gives up, and the tesseract process continues ad infinitum. Can you recommend core PHP tuning/configuration options that might address this behavior? We're not seeing any errors in logs that point to a definite root cause.
My team and I were theorizing why we see lingering tesseract "zombies" last night-- we have a 30 second max execution time on our nginx and php containers. We wonder if on occasion we receive a larger image into our API and it takes longer to execute the scan than the max time allows and thus leaving lingering processes. Do you think we could create some sort of exception handler when you call proc_open? I do see some examples of zombie process questions related to this on stack overflow. Many thanks for a great library!
Reported by @mbordash on Gitter:
Note to self: capture the PID and clean it up before returning. threat the processes just like the temp files
The text was updated successfully, but these errors were encountered: