From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Processes randomly get stuck
Date: Fri, 21 Aug 2015 08:31:00 -0000 [thread overview]
Message-ID: <20150821083125.GC19683@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20150821T100531-51@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
On Aug 21 08:09, Ismail Donmez wrote:
> Hi,
>
> Corinna Vinschen writes:
>
> >
> > On Jul 26 12:56, Ismail Donmez wrote:
> > > Hi,
> > >
> > > $ uname -a
> > > CYGWIN_NT-10.0 ux31a 2.2.0(0.289/5/3) 2015-07-23 20:41 x86_64 Cygwin
> > >
> > > For the last week or so ssh/zsh processes are randomly gets into
> defunct
> > > state, that is
> > >
> > > $ cat /proc/7232/cmdline
> > > <defunct>
> > > $ cat /proc/7232/status
> > > Name: zsh
> > > State: S (sleeping)
> > > Tgid: 7232
> > > Pid: 7232
> > > PPid: 5172
> > > Uid: 197609 197609 197609 197609
> > > Gid: 197609 197609 197609 197609
> > > VmSize: 7556 kB
> > > VmLck: 0 kB
> > > VmRSS: 10860 kB
> > > VmData: 2140 kB
> > > VmStk: 0 kB
> > > VmExe: 0 kB
> > > VmLib: 4644 kB
> > > SigPnd: 0000000000000000
> > > SigBlk: 0000000000000000
> > > SigIgn: 0000000000000000
> > >
> > > Same happens with ssh, and after some time like 5 minutes or so it
> goes
> > > back to the normal state. I wonder if anyone has been experiencing
> > > something similar?
> >
> > There's no change in 2.2.0 which might explain this, but still, did
> > you try to downgrade to 2.1.0?
>
> I tried to see the patterns of this problem before replying again. Because
> the bug randomly appears I can't conclude if 2.1.0 was any better (though
> I couldn't reproduce the problem with it.)
>
> I have an idea why this might be happening and want to ask what happens
> each time one does read /proc/<pid>/cmdline, does the function
> _pinfo::commune_request called everytime, or just once?
Every time. There's no caching mechanism for data fetched from /proc
files and the command line is only available inside the process itself.
> This might explain some behaviour I am seeing because tmux is reading that
> file every 20 seconds or something like that.
Oops.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-21 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 12:56 Ismail Donmez
2015-07-27 7:59 ` Corinna Vinschen
2015-08-21 8:15 ` Ismail Donmez
2015-08-21 8:31 ` Corinna Vinschen [this message]
2015-08-21 8:49 ` Ismail Donmez
2015-08-21 9:11 ` Corinna Vinschen
2015-08-21 9:23 ` Ismail Donmez
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=20150821083125.GC19683@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).