John Cupitt
libvips doesn't mind, you can fetch any size tile from any image.
Hi @kar-pev, You'll need to make a complete test program and a sample PDF before I can reproduce your problem. I tried here with this benchmark: ```python #!/usr/bin/python3 import sys...
`pdfload` won't make any difference, I was just trying to be clear. If you use `new_from_file` it'll work for any multi-page format, eg. GIF etc.
There's `thumbnail_buffer()` to thumbnail image data held as a string-like object, if that's what you mean.
Don't resize, just load at the correct size with `thumbnail`, then do any padding with `gravity`. You'll get better quality, lower memory use, and it'll be quicker too.
GreatGreat! (tangent, but it wasn't a memory leak -- that implies a memory reference has been lost due to a bug -- you were just seeing unexpectedly high memuse due...
Maybe your container isn't using popper to load PDFs, but is falling back to imagemagick? But that's just a guess, you need to share complete examples I can try before...
There's a lot of stuff you don't need in that dockerfile, I'd just have: ``` FROM python:3.9-slim RUN apt-get update \ && apt-get install -y \ build-essential \ pkg-config RUN...
Yes, I see about 1.5g with that file too. It has huge image overlays on every page, so I think that's to be expected. It's just a very heavy PDF.
I would guess it's memory fragmentation from handling those huge overlays.