Re: Debugging memory leaks/stale references

[Florian Weimer <fw@deneb.enyo.de>]

* Stefan Monnier:

> I think it would be worthwhile to start with the basic info returned by
> `garbage-collect' and such stuff.  See `memory-usage.el' below.
> [ I thought you already tried that, but the few lines above make me think
> that you don't even know whether the extra MBs are made up of cons cells, or
> strings, or non-elisp-data, or ...]

Others already did this.  But thanks anyway, I repeated the
experiment: The numbers indeed lack any distinct increase in
magnitude. 8-(

>> Are there any other objects that can change their size after
>> allocation?  (I'm pretty sure that there are no additional Lisp
>> objects allocated, but maybe an existing object grows without bounds.)
>
> Yes.  Things like the specpdl "stack", the matrices used in display, maybe
> the text-property-tree nodes, ...

Hmm, I'm going to gather a few more stats.

(And running Emacs under valgrind could prove helpful because I could
determine if the low-level allocator leaks memory.)