From: "Peter Kozich (UM)" <peter.kozich@upcmail.hu>
To: cygwin@cygwin.com
Subject: Re: Fork issue with timerfd
Date: Fri, 08 Mar 2019 19:56:00 -0000 [thread overview]
Message-ID: <ec73c62c9f6acefea7d07a45114460dc9bfc8c54.camel@upcmail.hu> (raw)
In-Reply-To: <20190306212324.GD3785@calimero.vinschen.de>
On Wed, 2019-03-06 at 22:23 +0100, Corinna Vinschen wrote:
> On Mar 6 21:54, Peter Kozich (UM) wrote:
> > In response to this one:
> >
> > Re: Fork issue with timerfd
> >
> > From: Achim Gratz <Stromeko at nexgo dot de>
> > To: cygwin at cygwin dot com
> > Date: Tue, 05 Mar 2019 20:15:32 +0100
> > Subject: Re: Fork issue with timerfd
> >
> > ....
> >
> > Anyway, the latest snapshot seemingly resolved that issue as
> > well, I can no longer reproduce it.
> >
> >
> > Unfortunately, only seemingly. Factually, the issue persists. And I
> > don't have to do anything with emacs just shoot up, wait cca. 20
> > seconds and it inevitably crashes, and it does so in the
> > foreground,
> > too:
> >
> > peter@D11934N ~
> > $ emacs .bash_history &
> > [2] 489
> > [1] Done emacs .bash_history
> >
> > 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.
>
>
> Thanks,
> Corinna
>
I tested this:
https://cygwin.com/snapshots/x86/cygwin1-20190308.dll.xz
emacs was on for a long time, did not crash and as far as could judge
it did not leak memory.
But it froze a couple of times which I cannot recall I have ever
experienced before. I mean it suddenly became deaf and dumb and while I
was actively editing the text, both the text area and the menu line got
unresponsive. I could only shut it down from the task manager, because
the red X didn't work either.
On the next week I will try the debug version in the hope that it can
make a trace or something helpful. Is there a guide somewhere how to
use it?
best regards
PK
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-08 19:56 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) [this message]
2019-03-08 20:10 ` Rockefeller, Harry
2019-03-08 20:22 ` Corinna Vinschen
2019-03-08 21:27 ` Rockefeller, Harry
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=ec73c62c9f6acefea7d07a45114460dc9bfc8c54.camel@upcmail.hu \
--to=peter.kozich@upcmail.hu \
--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).