bug#38345: 27.0.50; Permanent increase in memory consumption after opening images (or pdfs)

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> However, looking at the C code, I don't understand then why the
>> memory consumption is increasing. I can only see that too many images in
>> c->images array can cause extra memory consumption, which cannot cause
>> the observed memory leak.
>
> I guess that's because the freed memory is not at the end of the heap,
> and this cannot be returned to the OS.

This was half a year ago, and skimming this bug report, it seems like
this was the tentative conclusion -- there's no memory leak, just the
allocator not returning the memory back to the OS.

If that's the case, then this bug report can be closed?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no