Git development
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Domen Golob <domen.golob.px@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug: Git spawns subprocesses on windows
Date: Tue, 9 Jan 2024 22:56:07 +0000	[thread overview]
Message-ID: <ZZ3PB9mq8GTpGITC@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <CAF6dN-oEy-svp+6Bw_NAeOMrWc61ObcZ4Q2huVj9PPK1EQHquw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]

On 2024-01-09 at 15:33:43, Domen Golob wrote:
> Hello,
> the problem is exactly the same as what was reported here on stackoverflow:
> c# - Git for windows seems to create sub-processes that never die -
> Stack Overflow
> https://stackoverflow.com/questions/69579065/git-for-windows-seems-to-create-sub-processes-that-never-die
> 
> Additionally I have found out that:
> - a Git for Windows subprocess is created for each repository and
> every time a git command is issued this process grows in size and it
> never dies.
> - you cannot delete the .git folder from the terminal, but it works
> via file explorer
> - deleting the .git folder kills the Git for windows process
> - creating changes in several repos creates multiple processes, and
> sometimes the process is created as a subprocess

You probably want to contact Git for Windows at
https://github.com/git-for-windows/git.  The reason I suggest that is
that this is usually not a behaviour we see on Unix, and seems to be
Windows-specific.

I don't know if it's possible to see command-line arguments of processes
on Windows like it is with `ps` on Unix, but including that information
if possible will be very useful to the maintainers.  Without knowing
that information, it's very unlikely that anyone will be able to help
you since we don't know what's going on.

There are some possibilities of what's going on here:

* git gc is running.
* git maintenance or the fsmonitor is configured and is running.
* You have a non-default antivirus or monitoring software that causes
  processes to hang or not complete, so one of Git's subprocesses can't
  exit.  If you're using such software, we usually recommend completely
  removing it completely (disabling it is usually not sufficient),
  rebooting, and testing again to make sure it's not the problem.
* You have some other process which is running which spawns Git commands
  (editors, content indexers, etc.).
* We actually have a bug and some process is not waited for correctly,
  and zombie processes manifest differently on Windows than on Unix.
* Something else I haven't considered.

However, as I said, you'll probably want to contact the Git for Windows
folks through their issue tracker.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2024-01-09 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09 15:33 Bug: Git spawns subprocesses on windows Domen Golob
2024-01-09 22:56 ` brian m. carlson [this message]
2024-01-10  9:29   ` Domen Golob

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=ZZ3PB9mq8GTpGITC@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=domen.golob.px@gmail.com \
    --cc=git@vger.kernel.org \
    /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