Re: Collected crash information involving kkcc_marking, gc-incremental-traversal-threshold issue?

SJT> If I do M-x gnus-mime-save-part-and-strip on a fairly big SJT> attachment (say 5MB, IIRC) I can get a process to go from 150MB SJT> to 800MB in a real hurry (in terms of the number of XEmacs SJT> commands---of course on a 450MHz machine with 256MB of RAM, in SJT> terms of seconds it easily goes into the 000s). But that SJT> instance does not have newgc configured. I suspect it has SJT> something to do with KKCC, but I haven't tried configuring SJT> without KKCC yet. Does the memory footprint shrink again? SJT> I thought that one of the ideas behind the new collector and the SJT> KKCC algorithms was that almost everything was supposed to be SJT> allocated on the Lisp heap now? Yes, everything is supposed to be allocated on the Lisp heap, but we are not there yet. We still need to convert many additionally allocated objects to Lisp objects. -- Marcus