From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: posix_spawnp creates ghost processes
Date: Fri, 24 Apr 2020 08:47:42 -0400 [thread overview]
Message-ID: <41635049-2112-0d95-4adf-3e14f6f96029@cornell.edu> (raw)
In-Reply-To: <008201d61a0a$328a5510$979eff30$@gmail.com>
On 4/24/2020 3:30 AM, Kristian Ivarsson via Cygwin wrote:
> Hi all
>
> 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)
>
> 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 ?
Cygwin's posix_spawn uses execve under the hood. The latter creates a new
Windows process, does some housekeeping, and then transfers control from the old
process to the new one. There will be a short period of time when both
processes exist from the Windows point of view.
Ken
prev parent reply other threads:[~2020-04-24 12:47 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 ` Sv: " sten.kristian.ivarsson
2020-04-24 12:47 ` Ken Brown [this message]
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=41635049-2112-0d95-4adf-3e14f6f96029@cornell.edu \
--to=kbrown@cornell.edu \
--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).