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

Hello Marcus, sorry for not sending these out earlier, incrementally. Just swamped as many people here are. I attached the lisp and c stack information files atend. Last weekend I found following customizations in my (custom-set-variables ...) makes a big difference about XEmacs VM growth: '(gc-cons-incremental-threshold 2000000) '(gc-cons-percentage 0 t) '(gc-cons-threshold 20000000) '(gc-incremental-traversal-threshold 1000000) Firstly I have disabled GC based on gc-cons-percentage. Secondly I found setting gc-incremental-traversal-threshold 100 times higher than default avoids VM jumps during memory-intensive operations. Does this basically bring gc-incremental closer to being a gc-full? There are still situations where XEmacs VM growths in a big jump of a couple hundred MB, but the situations are a lot rarer now. Let me know of useful experiments (that would not take a whole lot of time). Later, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/