Re: window.c abort() crash in 21.4.6-14
Hrvoje Niksic <hniksic(a)xemacs.org> wrote:
> 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.
I don't see how the value 500 could be too low for anything resembling
normal usage. It's far more realistic to assume that we're still
seeing the infinite loop bug this used to guard against. :-(
That would be my guess, too. However, if commenting out the
abort() "fixes" the problem for Greg (as he seems to imply), and does
not cause an hang, then something else is going on ....
--
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.