X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 39ACC3858413 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1705674542; bh=6l72HnbIazb3swRQkd1p5NRGxuVd0Ekh7U19TqKpoL0=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=opxDbedB7mmTt/KBbtr1Qwz7tyPY6krPHtQ9Ctqk9GzVk1pG4Rp9uEO3xKlq6/kPf WA5mLTPbszfyWZAfdn47ZT3n2oJvX2w2hLDtGgmrdQlm+3JixaKHHpRu6X9R3h1l0B jORO689DdL4/aWP6mcW/rJnTTZ2NvzdRpV+tE+Tw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6D6BD3858D28 Date: Fri, 19 Jan 2024 15:28:40 +0100 To: cygwin AT cygwin DOT com Subject: Re: Possiblly bug of cygwin1.dll Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <20240119224436 DOT 876a055f356f7c6796bc725b AT nifty DOT ne DOT jp> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240119224436.876a055f356f7c6796bc725b@nifty.ne.jp> X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Jan 19 22:44, Takashi Yano via Cygwin wrote: > Hi, > > I might find the bug of cygwin1.dll (including 3.4.x, 3.5.0 (TEST)). > The following test case (c++ code) causes handle leak. > > This issue is reproducible with both g++ and clang++. > However, it does not happen in Linux environment. > So I guess this is the cygwin1.dlll bug. > > I looked into this problem a bit, and found number of event handle > increases every loop. > > I doubt pthread_mutex_xxx functions. > > #include > int func() { return 0; } > int main() > { > for (;;) { > std::future f = std::async(std::launch::async, func); > f.get(); > } > return 0; > } Can you create a plain C testcase from there? It's much easier to debug. Thanks, Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple