Memory leak when rendering pages about go-fitz HOT 2 CLOSED

That doesn't mean necessarily that there is a memory leak. MuPDF tries hard to maintain stuff in memory as much as possible for performance reasons so any font or image is held in memory. mutool for example have the option to limit memory, also imagemagick when working with PDF can consume a LOT of memory, and recommends -limit memory.

I now added FZ_NO_CACHE for all devices, so it doesn't try to cache everything. You can test if there are any differences, I don't see anything obviously wrong currenty that needs to be closed/freed.

from go-fitz.

With your changes, RAM usage does not increase nearly as fast, but by the end of a 132 page PDF, it still managed to get up to 1.1 GiB. It does seem to have improved, and if there are any issues it sounds as though they would be in the upstream library. So this issue could probably be closed.

However, I do question why so much RAM usage is necessary at all. I don't know much about how PDFs work, but I'm pretty sure that browsing the internet requires rendering far more complex information than would be found in an average PDF file, and while browsers do tend to use a fairly substantial amount of RAM, I have yet to see one eat it up quite like this.

from go-fitz.