public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <sten.kristian.ivarsson@gmail.com>
To: <cygwin@cygwin.com>
Subject: Sv: posix_spawnp creates ghost processes
Date: Fri, 24 Apr 2020 15:18:34 +0200	[thread overview]
Message-ID: <000101d61a3a$dbe03e60$93a0bb20$@gmail.com> (raw)
In-Reply-To: <94758478.20200424111042@yandex.ru>

> Greetings, Kristian Ivarsson via Cygwin!
> 
> > We're having a rather complex application and have noticed a rather
> > weird behaviour that I cannot find any information about
> 
> > We're using posix_spawnp and sometimes it creates extra "ghost-
> process(es)"
> > non visible to cygwin (via e.g. process status (ps)) but visible to
> > Windows (Task Manager)
> 
> Cygwin may spawn processes for housekeeping. F.e. if you "program &" in
> shell, an additional shell will be spawned to launch the "program" and
> notify the parent shell when it exits.
> 
> > The function doesn't fail and it doesn't report any error, but
> > sometimes (hard to reproduce deterministically) it creates one, or
> > more, extra processes of the same binary
> 
> > Have anyone noticed and/or have some information/ideas about this ?
> 
> Are these processes correctly exit when all childs exit?

Well, no

The issue is that due to some other issue, the main program hangs in some
kind of blocking mode (don't know why yet)

I exit that with SIGINT (via console and Ctrl+C) and there are a few
processes running that were created by posix_spawnp according to the CygWin
TTY, but according to Windows, some of the processes are duplicated
processes

If I kill -9 them in CygWin, the ones not visible are still running
according to Windows Task Manager

> --
> With best regards,
> Andrey Repin
> Friday, April 24, 2020 11:08:35
> 
> Sorry for my terrible english...



  reply	other threads:[~2020-04-24 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  7:30 sten.kristian.ivarsson
2020-04-24  8:10 ` Andrey Repin
2020-04-24 13:18   ` sten.kristian.ivarsson [this message]
2020-04-24 12:47 ` Ken Brown

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='000101d61a3a$dbe03e60$93a0bb20$@gmail.com' \
    --to=sten.kristian.ivarsson@gmail.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).