From owner-freebsd-questions  Wed Aug 13 22:36:44 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id WAA25136
          for questions-outgoing; Wed, 13 Aug 1997 22:36:44 -0700 (PDT)
Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA25131
          for <questions@FreeBSD.org>; Wed, 13 Aug 1997 22:36:42 -0700 (PDT)
From: grog@lemis.com
Received: from papillon.lemis.com by suntan.tandem.com (8.6.12/suntan5.970212) 
	id WAA02044; Wed, 13 Aug 1997 22:36:33 -0700
Received: (grog@localhost) by papillon.lemis.com (8.8.4/8.6.12) 
       id OAA00327; Thu, 14 Aug 1997 14:26:34 +0900 (JST)
Message-Id: <199708140526.OAA00327@papillon.lemis.com>
Subject: Re: Anyone noticed the new FreeBSD Netscape looping?
In-Reply-To: <33F1B44F.140BF509@brady.appliedtheory.com> from Michael Brady at "Aug 13, 97 09:19:12 am"
To: mbrady@appliedtheory.com
Date: Thu, 14 Aug 1997 14:26:33 +0900 (JST)
Cc: questions@FreeBSD.org (FreeBSD Questions)
Organisation:   LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone:          +61-8-8388-8250
Fax:            +61-8-8388-8250
Mobile:         +61-41-739-7062
WWW-Home-Page:  http://www.lemis.com/~grog
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Michael Brady writes:
> Mike O'Brien wrote:
>
>>         I've noticed that the new FreeBSD-specific Netscape 4.02b<whatever>
>> seems to have a tendency to go into a hard loop upon trying to exit.
>>
>>         However, this looping behavior is worrisome because it doesn't
>> happen every time, just 2/3 of the time.  This Is Not Good.
>
> This happens on my workstation too (I'm running 2.2.2, 40MB) when Netscape
> exits (never when it opens). It only happens when Java was loaded onto the
> browser to view pages with applets. All the windows close, yet the process
> remains and absorbs all the cpu in an infinite RUN state. The only way to kill
> it is with a kill -9. It sucks.
>
> I'm going to try a ktrace the next time it happens to see whats going on.

Don't bother.  It's looping on a SIGALRM.  Since it calls
gettimeofday() (or some such) every time, it looks as if it's
miscalculating a parameter to alarm().

Greg