Re: window.c abort() crash in 21.4.6-14
gak(a)klanderman.net (Greg Klanderman) wrote:
I've been seeing xemacs abort in the following code in window.c:
That code is there, in theory, to catch any "infinite loop"
problems in window_loop().
Do you have a lot of XEmacs "windows" (i.e., frames split multiple
times into multiple "XEmacs windows", not actual X11 windows)? I'm
wondering if the "500" value is too low, when lots of XEmacs
"windows"
are present. Maybe something like "10000" might be a better number
(especially if your XEmacs works fine, and does not hang, when you
comment out the call to abort()).
[ For that matter, is it possible to have non-visible XEmacs windows? I
believe not, but I do not know this for a fact. If it is possible,
that could cause this problem. Hmmm. Could killed windows be
(temporarily?) sticking around in the window list? ]
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.