From owner-freebsd-questions@FreeBSD.ORG  Sun Feb 15 21:06:47 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5729016A4CE
	for <freebsd-questions@freebsd.org>;
	Sun, 15 Feb 2004 21:06:47 -0800 (PST)
Received: from host7.globalnameservers.com (host7.globalnameservers.com
	[209.239.34.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0136E43D1F
	for <freebsd-questions@freebsd.org>;
	Sun, 15 Feb 2004 21:06:47 -0800 (PST)
	(envelope-from drc7257@cs.rit.edu)
Received: from cs.rit.edu (roc-66-67-196-34.rochester.rr.com [66.67.196.34])
	i1G56kdi015066
	for <freebsd-questions@freebsd.org>; Mon, 16 Feb 2004 00:06:46 -0500
Message-ID: <40305158.4090101@cs.rit.edu>
Date: Mon, 16 Feb 2004 00:12:56 -0500
From: "Daniel R. Curran" <drc7257@cs.rit.edu>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US;
	rv:1.6b) Gecko/20040209 Thunderbird/0.4
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Firefox Process Not Exiting
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Feb 2004 05:06:47 -0000

I am wondering if anyone else has this issue and if there is a fix for 
it. When I run firefox and then exit the program the process remains 
resident, and it starts eating up the CPU. Does anyone know of a fix for 
this. I have been manually killing the process, but this seems like a 
horrible way to work with the program.

-Dan-