X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=fM6Ggzl5NP/mQHedYSa2J48YZgzCy2IE0mcDVL9mP52zYHZbj4enh
	Ba9UCNQMI9qHnCR/s3ewuRNTjz3d3VEAjoI9Xu3LXW8HYxFEHrXiw07/xlK6H+rO
	GhXwR8rI5fUvXUe7Y/xcyqGAv71m2IW+JTZoWdDwOlqolm/NAzX8zY=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=rZqN4D0QqNbwHe7jZlpyklsjwAM=; b=nhuhleqahyNYbBFATfqRtDvggvqz
	y2xNa/7BHaqjy7xLZKyl/LMEVxf+fE1uUSIPA7V4njOaD3M0ZZtDTS4VmDZgSD4k
	hZ//U6lAIeFftAqICOdOvv6Cugaah62xvK3YWy9k78TcfhYpSCEBcAKxEu6gTj6Y
	gtLbh8+pJX513HM=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-102.3 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=mouse, 0308, hangs, heck
X-HELO:	mout.kundenserver.de
Date:	Fri, 8 Mar 2019 21:22:05 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	Ken Brown <kbrown AT cornell DOT edu>
Cc:	cygwin AT cygwin DOT com
Subject:	Re: Fork issue with timerfd
Message-ID:	<20190308202205.GR3785@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	Ken Brown <kbrown AT cornell DOT edu>, cygwin AT cygwin DOT com
References:	<67d143c997f2d873435647acebd2226c4e8661d3 DOT camel AT upcmail DOT hu> <20190306212324 DOT GD3785 AT calimero DOT vinschen DOT de> <ec73c62c9f6acefea7d07a45114460dc9bfc8c54 DOT camel AT upcmail DOT hu> <9d6bb43680524d3ab7878ae7a0cae233 AT vsrv060ex03 DOT ssd DOT fsi DOT com>
MIME-Version:	1.0
In-Reply-To:	<9d6bb43680524d3ab7878ae7a0cae233@vsrv060ex03.ssd.fsi.com>
User-Agent:	Mutt/1.11.3 (2019-02-01)

--LP3HGykwGcUp63ex
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar  8 20:10, Rockefeller, Harry wrote:
> > > > peter AT D11934N ~
> > > > $       1 [main] emacs 489 C:\CygWin\bin\emacs-w32.exe: *** fatal
> > > > error -
> > > > CreateThread failed for pipesel - 0x0<0x0>, Win32 error 8
> > >
> > > I couldn't directly reproduce this issue, but I saw emacs using more
> > > an more memory while the cursor was blinking.  I found a resource leak
> > > in posix timers which was probably the cause for this problem.
> > >
> > > I pushed a patch and uploaded new developer snapshots to
> > > https://cygwin.com/snapshots/
> > >
> > > Please test.
> > I tested this:
> > https://cygwin.com/snapshots/x86/cygwin1-20190308.dll.xz
>=20
> > emacs was on for a long time, did not crash and as far as could judge i=
t did not leak memory.
>=20
> > But it froze a couple of times which I cannot recall I have ever experi=
enced before. I mean it suddenly became deaf and dumb and while I > > was a=
ctively editing the text, both the text area and the menu line got unrespon=
sive. I could only shut it down from the task manager,
> > because the red X didn't work either.

What the heck.  The 0308 snapshot was supposed to fix these hangs as
described in https://cygwin.com/ml/cygwin/2019-03/msg00160.html

Are you sure it was the 0308 snapshot and not by any chance the 0306 one?

I can't reproduce this with 0308.  I'm typing lots and lots in emacs,
doing copy/paste with the mouse, and it just works with 0308.

> > On the next week I will try the debug version in the hope that it can m=
ake a trace or something helpful. Is there a guide somewhere how to > use i=
t?

Install the cygwin1.dbg file into /bin and When Emacs hangs, attach with
gdb and print the backtrace of each thread.  That should give a hint.

> I have been running https://cygwin.com/snapshots/x86/cygwin1-20190306.dll=
.xz , i.e., March 6th
> For a couple hours yesterday and all day today along with Ken Brown's tes=
t version of emacs (GNU Emacs 26.1.92)
> And have not had a hiccup.
> (Well, to be truthful, I'm running a lot more of Ken Brown's test softwar=
e than just emacs.)

Can you please test the 0308 snapshot with stock emacs, too?

Ken, any chance you could test this as well?  If there really are still
hangs with current emacs and the 0308 snapshot, I might need a bit of
help.  Some kind of reproducer or some input as to the nature of the
hangs would be nice.


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--LP3HGykwGcUp63ex
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyCzu0ACgkQ9TYGna5E
T6Dl+g/9GzoAT0PVYpqeISFgotq9zke7KBcNlu76F/XPAnSR5SQLs3/oTH0kjeTq
xCTeKrH7JC03vAXHiuP0X6VidZr57W6YHozGuxpwJqnzV5AR2aiDGhJiwWipzchn
0/gD+ho+m6xWx7/UOgf3yG9CxTVuZkCefq8HcMqib3ZLXoVq73SWEnRKm8I+VLkD
fJwmiR92JyjNaPVNeTxdWwDAzuI9d52Nbi9QWcESCnGng+ayPUKVBNyH4bDGiVAQ
78CkcU8ZBUPS+UMgrfhuF8LKvBPZyz16U3G6Bj03d2869YLBquvdVH3y4ucymV3Q
YW6ImdUTU5l3/xAiaLA3m6D67F+9Y8rFiort2VreinjILtjOWH8Jl0So5tJQshJE
ukjYS+ymA0xNdbiVHTVNBR9EixS/6QtljdVRyZrNaAOrm8mfuS2LCcFC8L42yPbe
UTgKduE2aKHQft8CoBGSk69pwZH0Rkpnywlfvxkw09mnsf5U9hJcWV/3brulgLLx
LrETFW+ZzeAEDztWt/iw+BKG7/fDrw8jESXfk64Miy5bNUp9Yt5vGm2mrCQ6HtNw
n+zoXYFtJx863E9jY6FwM202r2HuVrPvGPWhEMAK8mpGROZhDEJx+ziEJ+bWYgig
GdzlUAtrQ25yCPGP6dWxUtgltUlGljJH6qaX9/NQKpsf1vgVbiA=
=xQWo
-----END PGP SIGNATURE-----

--LP3HGykwGcUp63ex--

- Raw text -