bug#43389: 28.0.50; Emacs memory leaks

[DJ Delorie]

Florian Weimer <fweimer@redhat.com> writes:
> But how helpful would that be, given that malloc_info does not really
> show any inactive memory (discounting my 200 MiB hole)?

One doesn't know how helpful until after looking at the data.  If RSS is
going up fast, something is calling either sbrk or mmap.  If that thing
is malloc, a trace tells us if there's a pattern.  If that pattern
blames the lisp allocator, my job here is done ;-)