From owner-freebsd-ports@FreeBSD.ORG  Tue May  6 05:32:44 2008
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id E9EA71065673
	for <ports@FreeBSD.org>; Tue,  6 May 2008 05:32:44 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3])
	by mx1.freebsd.org (Postfix) with ESMTP id E08D18FC1E
	for <ports@FreeBSD.org>; Tue,  6 May 2008 05:32:44 +0000 (UTC)
	(envelope-from jdc@parodius.com)
Received: by mx01.sc1.parodius.com (Postfix, from userid 1000)
	id 9BD8D1CC05B; Mon,  5 May 2008 22:32:44 -0700 (PDT)
Date: Mon, 5 May 2008 22:32:44 -0700
From: Jeremy Chadwick <koitsu@freebsd.org>
To: Matt <datahead4@gmail.com>
Message-ID: <20080506053244.GA94936@eos.sc1.parodius.com>
References: <cd6b4a5b0805052220i87f274fnd5f08618d9a72fef@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <cd6b4a5b0805052220i87f274fnd5f08618d9a72fef@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Cc: ports@FreeBSD.org, amistry@am-productions.biz
Subject: Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon
	process(es) stuck
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2008 05:32:45 -0000

On Tue, May 06, 2008 at 12:20:17AM -0500, Matt wrote:
> The symptom is as described above - the gvfs-fuse-daemon processes do
> not exit cleanly and more processes continue to build-up whenever I
> complete an X-session.  The processes do exit when I send them a
> manual kill signal.  The only info I have at this point is a backtrace
> from a "stuck" process.  Hopefully it will be useful in identifying
> the issue.

What makes it "stuck?"  What state is the process in?  ps or top output
would've been helpful, ditto with truss or ktrace output.  Is it eating
100% CPU (e.g. read() is continually being called without handling error
conditions), or does it just sit there idling?

> (gdb) bt
> #0  0x1045d3d1 in read () from /lib/libc.so.7
> #1  0x10379792 in read () from /lib/libthr.so.3
> #2  0x1035a67b in fuse_kern_chan_receive (chp=0xbf9fef8c,
> buf=0x1055c000 "", size=135168) at fuse_kern_chan.c:28
> #3  0x1035fb13 in fuse_chan_recv (chp=0xbf9fef8c, buf=0x1055c000 "",
> size=135168) at fuse_session.c:184
> #4  0x1035aac6 in fuse_do_work (data=0x10517580) at fuse_loop_mt.c:70
> #5  0x1037ab1f in pthread_getprio () from /lib/libthr.so.3
> #6  0x00000000 in ?? ()

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |