Re: Collected crash information involving kkcc_marking, gc-incremental-traversal-threshold issue?
Marcus Crestani writes:
In my observations I see the growth in the virtual memory (with
`top')
but not in the Lisp heap (`show-object-memory-usage-stats'). Can you
confirm this?
I see this.
I got a recipe from one of my colleagues who is using
gnus with nnml folders: Open an nnml summary buffer with many (>2,000)
mails, the virtual memory of the XEmacs process increases 200--300MB,
the Lisp heap increases only 1--2MB.
If I do M-x gnus-mime-save-part-and-strip on a fairly big attachment
(say 5MB, IIRC) I can get a process to go from 150MB to 800MB in a
real hurry (in terms of the number of XEmacs commands---of course on a
450MHz machine with 256MB of RAM, in terms of seconds it easily goes
into the 000s). But that instance does not have newgc configured. I
suspect it has something to do with KKCC, but I haven't tried
configuring without KKCC yet.
I thought that one of the ideas behind the new collector and the KKCC
algorithms was that almost everything was supposed to be allocated on
the Lisp heap now?
Steve