Maybe it's connected also to the underlying infrastructure? We are
getting this in AWS lambda jobs and we're hitting a system limit of
max processes because of it.
Can you try running this inside this image public.ecr.aws/lambda/python ?

On Sun, Sep 10, 2023 at 9:47 PM Taylor Blau [off-list ref] wrote:

On Sun, Sep 10, 2023 at 12:47:14PM +0300, Max Amelchenko wrote:

quoted

Output of second ps aux command (after running git clone):

bash-4.2# ps aux

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND

root         1  0.0  0.0 715708  5144 pts/0    Ssl+ 09:43   0:00
/usr/local/bin/aws-lambda-rie /var/runtime/bootstrap

root        14  0.0  0.0 114096  3088 pts/1    Ss   09:43   0:00 bash

root       167  0.5  0.0      0     0 pts/1    Z    09:46   0:00 [ssh] <defunct>

root       168  0.0  0.0 118296  3408 pts/1    R+   09:46   0:00 ps aux

See the added ssh defunct process.

Hmm... I wasn't quite able to reproduce this locally. Below
`git.compile` points to a Git executable built from the v2.40.1 tag
corresponding to your bug report:

    $ host='ssh://*****@*****lab-prod.server.sim.cloud/terraform/modules/aws-eks'
    $ git.compile clone "$host" /tmp/x
    Cloning into '/tmp/x'...
    ssh: Could not resolve hostname *****lab-prod.server.sim.cloud: Name or service not known
    fatal: Could not read from remote repository.

    Please make sure you have the correct access rights
    and the repository exists.

and then:

    $ ps aux | grep defunct
    ttaylorr 3688844  0.0  0.0   6340  2180 pts/1    S+   14:45   0:00 grep --color defunct

Thanks,
Taylor