X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: 4355 pipe handlers open at once - is this to be 'expect'ed? Date: Tue, 21 Mar 2006 19:20:17 -0000 Message-ID: <00a901c64d1c$7cafd900$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <442050CF.209EE687@dessent.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 21 March 2006 19:15, Brian Dessent wrote: > Dave Korn wrote: > >> I thought the value for hProcess looked a little suspiciously high, but >> on digging through it with Process Explorer (which appears to be playing >> nicely with cygwin programs these days) discovered that it was a real >> process handle value, because expect.exe had over four thousand anonymous >> pipes open: > > I noticed this a few months ago. At the end of running the full gcc > testsuite there were over 60,000 handles in the expect.exe process, the > vast majority of which were these anonymous pipes that you show below. > > I tried to reproduce it with a looping dummy "hello world" test harness > but couldn't. I think it's something particular in the (quite > customized) gcc 'expect' harness. > > Brian Hmm, I reckon the most likely thing is that expect for some reason isn't actually fully draining the pipe, or maybe just not closing the fd.... I'll probably have to build it from source and take a look. Thanks for confirming it's not just something freaky at my end. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/