Adrian Aichner <adrian(a)xemacs.org> writes:
gc.c has this:
struct
{
enum gc_phase phase;
EMACS_INT n_gc[GC_STAT_COUNT];
EMACS_INT n_cycles[GC_STAT_COUNT];
EMACS_INT enqueued[GC_STAT_COUNT];
EMACS_INT dequeued[GC_STAT_COUNT];
EMACS_INT repushed[GC_STAT_COUNT];
EMACS_INT enqueued2[GC_STAT_COUNT];
EMACS_INT dequeued2[GC_STAT_COUNT];
EMACS_INT finalized[GC_STAT_COUNT];
EMACS_INT freed[GC_STAT_COUNT];
EMACS_INT explicitly_freed;
EMACS_INT explicitly_tried_freed;
} gc_state;
Here is a snapshot before the second wrap around of the numbers in
enqueued and dequeued:
Here is the same after the second wrap-around:
And here is latest data showing the wrap-around of freed.
It's remarkable with all this memory use that this XEmacs instance
keeps going and being useful for gnus and general editing.
Marcus, I hope this data will help you to identify general areas where
memory is leaking.
face-cachel has now surpassed the amount of memory used by cons cells.
Best regards,
Adrian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/