From xemacs-m  Wed Mar 12 06:40:05 1997
Received: from beavis.bayserve.net (jmiller@port3.bayserve.net.244.148.206.in-addr.arpa [206.148.244.99])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id GAA09844
	for <xemacs-beta@xemacs.org>; Wed, 12 Mar 1997 06:40:03 -0600 (CST)
Received: (from jmiller@localhost) by beavis.bayserve.net (8.7.5/8.7.3) id HAA01261; Wed, 12 Mar 1997 07:44:43 -0500
Date: Wed, 12 Mar 1997 07:44:43 -0500
Message-Id: <199703121244.HAA01261@beavis.bayserve.net>
From: Jeff Miller <jmiller@bayserve.net>
To: xemacs-beta@xemacs.org
Subject: 20.1-b6: sit-for and accept-process-output
In-Reply-To: <QQcgmy07372.199703120600@crystal.WonderWorks.COM>
References: <QQcgmy07372.199703120600@crystal.WonderWorks.COM>
Reply-to: jmiller@bayserve.net
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: text/plain; charset=US-ASCII

>>>>> "KJ" == Kyle Jones <kyle_jones@wonderworks.com> writes:

KJ> I have a feeling something is rotten between sit-for and
KJ> accept-process-output.  I have seen XEmacs go into a spin several
KJ> times now, where I know sit-for was called around the same time that
KJ> VM's POP client went looking for mail.  C-g will break out of it
KJ> sometimes, but sometimes it won't.  Senidng a SIGINT will break the
KJ> loop in those cases.  This isn't new to b6.  Only recently have I
KJ> become convinced that it isn't filladapt looping or some timer code
KJ> bug, which I had been suspecting since I've been hacking on all that
KJ> stuff.

This sounds a lot like what I was seeing on Sun with 19.15-b98 as well.  I
had vm lock up about 6 times when it was doing mail checks.  I finally
just turned off the mail check.  Things have been reasonably stable since.

This only started hitting me with the latest 19.15 beta though.

Linux 2.0.27/libc 5.3.12/gcc2.7.2 



