[BUG] Celeryd getting killed with OOM about paperless-ngx HOT 4 CLOSED

Ps. A couple more things: the PDF looks like it’s all images, it sounds like images of words, which are always the most ‘expensive’. Also, you can always try running it directly against ocrmypdf yourself to see

from paperless-ngx.

I’m not sure there’s much for us to do here, as noted in the template (link is there too), and you can see in the logs the OCR process is handled by ocrmypdf. In general I have no idea how receptive they are to this kind of report (ie they might just say “OCR is resource-intensive”) but could still be worth opening an issue there, certainly seems unexpected. That said, I think you would need to supply a PDF.

Feel free to link to the issue back here if you do, in general we don’t use our issues to track upstream problems so we’ll close this.

If another team member notices something I didn’t here they can always re-open.

thanks

from paperless-ngx.

Thanks for the advice, that's probably what it is.

from paperless-ngx.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.

from paperless-ngx.