DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 62NAOvcP3456651
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 62NAOvcP3456651
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=Ozj1VGaB
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 3298A4BAE7C3
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1774261496;
	bh=S9v6LExm72yDU86OlXLO+tguFajlPH5mHnkmm33jCOg=;
	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=Ozj1VGaB6jt7iafO4zNNJTO5MQtUVv/AmziP5ALnzr/bPubJ5zFJ/AZf3y9/JkTF/
	L/nvj7zEzBSRCxHr3sqQuTkngtDeUg4sCE3W4wTMlpQ9AnleMbmJWr/o/GOE0JCc7A
	HA/vBztClb/2ga1qsjbnRQ4A/fseAigv6DOguV7I=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 27CD44B9DB71
Date:	Mon, 23 Mar 2026 11:24:37 +0100
To:	ASSI <Stromeko AT nexgo DOT de>
Subject:	Re: std::mutex bug: Windows handle growth
Message-ID:	<acEU5Zu2SBB72-2F@calimero.vinschen.de>
Mail-Followup-To:	ASSI <Stromeko AT nexgo DOT de>, cygwin AT cygwin DOT com
References:	<2d48a740-ce2b-4259-8947-f5c875dd1672 AT hvc DOT rr DOT com>
	<87tsu97xr1 DOT fsf AT Gerda DOT invalid>
MIME-Version:	1.0
In-Reply-To:	<87tsu97xr1.fsf@Gerda.invalid>
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>, cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi Achim,

On Mar 21 21:06, ASSI via Cygwin wrote:
> Frank Eskesen via Cygwin writes:
> > I've run into a problem that occurs on Cygwin that doesn't occur on
> > Linux systems: When a std::mutex is used, it doesn't clean up a
> > Windows handle that it uses.
> 
> I've applied the fix provided by Corinna and built a test version on top
> of the current gcc-13.4 snapshot.  Please test.
> 
> https://repo.or.cz/gcc/cygwin-gcc.git/commitdiff/f3429b7ec960fea9df62bc3c14e257d60fe436f0
> 
> The bug was already reported upstream a long time ago as FreeBSD also
> has an implementation where the mutex can not be destroyed trivially:
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71684

Reading this bug report, wouldn't just defining
_GTHREAD_USE_MUTEX_INIT_FUNC for Cygwin have the same effect?


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

- Raw text -