From owner-freebsd-current@FreeBSD.ORG Mon Jun 7 18:37:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 485BC16A4CE for ; Mon, 7 Jun 2004 18:37:10 +0000 (GMT) Received: from email11.aon.at (WARSL402PIP7.highway.telekom.at [195.3.96.94]) by mx1.FreeBSD.org (Postfix) with SMTP id E38EB43D58 for ; Mon, 7 Jun 2004 18:37:08 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 459076 invoked from network); 7 Jun 2004 18:37:07 -0000 Received: from n754p010.dipool.highway.telekom.at (HELO ?212.183.104.42?) ([212.183.104.42]) (envelope-sender ) by qmail2rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 7 Jun 2004 18:37:07 -0000 From: Stefan Ehmann To: Brian Feldman In-Reply-To: <20040607172431.GA19790@green.homeunix.org> References: <1086511629.1509.13.camel@taxman> <20040607172431.GA19790@green.homeunix.org> Content-Type: text/plain Message-Id: <1086633425.1020.15.camel@taxman> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 07 Jun 2004 20:37:05 +0200 Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: esd leaking file descriptors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 18:37:10 -0000 On Mon, 2004-06-07 at 19:24, Brian Feldman wrote: > On Sun, Jun 06, 2004 at 10:47:09AM +0200, Stefan Ehmann wrote: > > When i run mpg321 -o esd foo.mp3 (or any other player that uses esd as > > output) lsof shows an increasing number of open files. It increases at a > > rate of about 50 files per second. System will run out of file > > descriptor eventually. > > > Check if esd is encountering exceptional conditions with the ktrace > facility. You will wnat to run esd with ktrace(1) and then use > kdump(1) to view the log of system calls. The other PC probably > also doesn't have the same hardware, so it's not so easy to see if > it's just a bug in -CURRENT. I just tried a kernel from June, 1st: esd doesn't leak any file descriptors. So it's definitely a CURRENT problem. I couldn't spot anything suspicous using ktrace (That is no notable difference compared to the other machine). Here are two excerpts from kdump output that basically repeat all the time: 1262 esd RET read 4096/0x1000 1262 esd CALL write(0x8,0x8059000,0x1000) 1262 esd GIO fd 8 wrote 4096 bytes ... 1262 esd RET write 4096/0x1000 1262 esd CALL gettimeofday(0xbfbfe598,0) 1262 esd RET gettimeofday 0 1262 esd CALL select(0xa,0xbfbfe510,0,0,0xbfbfe508) 1262 esd RET select 1 1262 esd CALL accept(0x7,0xbfbfe580,0xbfbfe528) 1262 esd RET accept -1 errno 35 Resource temporarily unavailable 1262 esd CALL select(0xa,0xbfbfe4f0,0,0,0xbfbfe478) 1262 esd RET select 1 1262 esd CALL read(0x9,0x805c000,0x1000) 1262 esd GIO fd 9 read 4096 bytes