From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Fork issue with timerfd
Date: Fri, 08 Mar 2019 21:27:00 -0000 [thread overview]
Message-ID: <c2f6e2a2b10c490691d1ce01bc820cdc@vsrv060ex03.ssd.fsi.com> (raw)
In-Reply-To: <20190308202205.GR3785@calimero.vinschen.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1906 bytes --]
[snip]
> > > > peter@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 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.
[snip]
> 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 test 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
> > software than just emacs.)
> Can you please test the 0308 snapshot with stock emacs, too?
I am testing with https://cygwin.com/snapshots/x86/cygwin1-20190308.dll.xz and stock (26.1) emacs now.
I see no hangup so far. You're not going crazy Corinna.
> 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.
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
next prev parent reply other threads:[~2019-03-08 21:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 20:55 Peter Kozich (UM)
2019-03-06 21:23 ` Corinna Vinschen
2019-03-08 19:56 ` Peter Kozich (UM)
2019-03-08 20:10 ` Rockefeller, Harry
2019-03-08 20:22 ` Corinna Vinschen
2019-03-08 21:27 ` Rockefeller, Harry [this message]
2019-03-09 15:38 ` Corinna Vinschen
2019-03-08 22:04 ` Ken Brown
2019-03-09 12:35 ` Ken Brown
2019-03-09 15:38 ` Corinna Vinschen
2019-03-09 18:48 ` Ken Brown
2019-03-09 19:08 ` Corinna Vinschen
2019-03-08 22:21 ` Peter Kozich (UM)
2019-03-08 22:44 ` Peter Kozich (UM)
2019-03-09 15:39 ` Corinna Vinschen
2019-03-11 18:25 ` Peter Kozich (UM)
-- strict thread matches above, loose matches on Subject: below --
2019-02-24 18:55 Ken Brown
2019-02-24 19:01 ` Corinna Vinschen
2019-02-24 19:53 ` Corinna Vinschen
2019-02-24 23:42 ` Corinna Vinschen
2019-02-25 3:21 ` Ken Brown
2019-02-25 7:10 ` Ken Brown
2019-02-25 10:51 ` Corinna Vinschen
2019-02-25 22:01 ` Corinna Vinschen
2019-02-26 3:12 ` Ken Brown
2019-02-26 9:01 ` Corinna Vinschen
2019-02-26 9:37 ` Corinna Vinschen
2019-02-26 11:46 ` Corinna Vinschen
2019-02-26 15:05 ` Ken Brown
2019-02-27 16:24 ` Corinna Vinschen
2019-02-27 16:39 ` Ken Brown
2019-02-27 19:31 ` Corinna Vinschen
2019-03-04 18:13 ` Achim Gratz
2019-03-04 21:46 ` Ken Brown
2019-03-05 19:15 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2f6e2a2b10c490691d1ce01bc820cdc@vsrv060ex03.ssd.fsi.com \
--to=harry.rockefeller@flightsafety.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).