Re: window.c abort() crash in 21.4.6-14

Thursday, 13 November 2003

Hi Darryl and Hrvoje,

...
>>>> Darryl Okahata <darrylo(a)soco.agilent.com&gt;
writes: 
...
 Hrvoje Niksic <hniksic(a)xemacs.org&gt; 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. 
No, I typically have at most 5 frames (total across two displays) of
at most two windows each, and I've got 50-100 buffers if that matters.

...
> 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 .... 
Well, I just commented out that abort() yesterday, so it's too early
to tell.  But, as long as the "break" is there, it should not hang.
Maybe I should put a printf() in so I know I've hit it at least..
what other data would be useful?

thanks,
greg

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998