Date: Mon, 5 May 2008 22:32:44 -0700 From: Jeremy Chadwick <koitsu@freebsd.org> To: Matt <datahead4@gmail.com> Cc: ports@FreeBSD.org, amistry@am-productions.biz Subject: Re: FreeBSD Port: fusefs-libs-2.7.2_1 - gvfs-fuse-daemon process(es) stuck Message-ID: <20080506053244.GA94936@eos.sc1.parodius.com> In-Reply-To: <cd6b4a5b0805052220i87f274fnd5f08618d9a72fef@mail.gmail.com> References: <cd6b4a5b0805052220i87f274fnd5f08618d9a72fef@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080506053244.GA94936>