From owner-freebsd-hackers@FreeBSD.ORG  Tue Aug 31 12:19:51 2010
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 635C410656B0;
	Tue, 31 Aug 2010 12:19:51 +0000 (UTC) (envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 32E9F8FC17;
	Tue, 31 Aug 2010 12:19:51 +0000 (UTC)
Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net
	[66.111.2.69])
	by cyrus.watson.org (Postfix) with ESMTPSA id D389A46B7E;
	Tue, 31 Aug 2010 08:19:50 -0400 (EDT)
Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9])
	by bigwig.baldwin.cx (Postfix) with ESMTPSA id BB8088A04F;
	Tue, 31 Aug 2010 08:19:47 -0400 (EDT)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-hackers@freebsd.org
Date: Tue, 31 Aug 2010 07:53:49 -0400
User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; )
References: <AANLkTimCZsan9y+n=V1pHnT1q=9iWHbwc2cnJGyOz90k@mail.gmail.com>
	<AANLkTikaCjM+JFjAGDefoiQHLDbhdpSyg+uxiGmmswON@mail.gmail.com>
	<AANLkTi=KAgk14wf7Z=a=CNgyEAPDnyRtM8bjZDanbfzV@mail.gmail.com>
In-Reply-To: <AANLkTi=KAgk14wf7Z=a=CNgyEAPDnyRtM8bjZDanbfzV@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201008310753.49567.jhb@freebsd.org>
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1
	(bigwig.baldwin.cx); Tue, 31 Aug 2010 08:19:47 -0400 (EDT)
X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham
	version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx
Cc: Davide Italiano <davide.italiano@gmail.com>, Andriy Gapon <avg@icyb.net.ua>,
	Garrett Cooper <gcooper@freebsd.org>
Subject: Re: System freezes unexpectly
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 12:19:51 -0000

On Monday, August 30, 2010 12:45:40 pm Garrett Cooper wrote:
> On Mon, Aug 30, 2010 at 9:24 AM, Davide Italiano
> <davide.italiano@gmail.com> wrote:
> > removing ~/.mozilla works fine. I think that problem's related to
> > add-on Xmarks I've been installer or to "Restore session"
> > functionality
> 
> It would have been interesting to capture what `froze' the machine, in
> particular because it could have been a valuable bug for either
> Mozilla to capture and fix, or for us to capture and fix. Unless your
> machine doesn't meet the hardware requirements, I don't see a reason
> why a userland application should lock up a system.
> 
> There are other ways you can debug this further, using -safe-mode as a
> next step, then choose to not restore the last session (which is
> available from within the javascript settings file -- nsPrefs.js?).

If only firefox is frozen, then you can always ssh in from another machine and 
use top/ps, etc., or even gdb on the firefox process itself.

-- 
John Baldwin