From: Bagas Sanjaya <bagasdotme@gmail.com>
To: 程洋 <chengyang@xiaomi.com>, "git@vger.kernel.org" <git@vger.kernel.org>
Cc: 何浩 <hehao@xiaomi.com>, "Xin7 Ma 马鑫" <maxin7@xiaomi.com>
Subject: Re: Git fork process infinitely and never stop
Date: Tue, 5 Jul 2022 19:32:56 +0700 [thread overview]
Message-ID: <8e1d019e-6456-ed05-7d3e-a0c4beeb35fa@gmail.com> (raw)
In-Reply-To: <9d3b79239a314f72a099040a26ef9ad8@xiaomi.com>
On 7/4/22 16:44, 程洋 wrote:
> Git Version: 2.36.1
>
> In some circumstance, Git will fork child process forever until my PC crash.
> I don’t understand why and I don’t know what log or information I should provide
> Details are showed in this Youtube video. Please feel free to ask if I can provide anything.
>
Hi and welcome to Git mailing list!
For this bug report to be useful, please include following information,
inline in your email:
- git version
- steps to reproduce the bug
- what you expect and actual behavior, as well as the differences
- system info
- miscellaneous
And don't forget to send as plaintext email.
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-07-05 13:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 9:44 Git fork process infinitely and never stop 程洋
2022-07-05 12:32 ` Bagas Sanjaya [this message]
2022-07-05 15:25 ` [External Mail]Re: " 程洋
2022-07-05 22:50 ` Ævar Arnfjörð Bjarmason
2022-07-06 5:34 ` Johannes Sixt
2022-07-06 7:21 ` lilinchao
2022-07-06 14:03 ` 回复: " 程洋
[not found] ` <11f76b2382934edcb97eb201f0a78a67@xiaomi.com>
2022-07-07 17:54 ` 程洋
2022-07-08 10:45 ` 程洋
2022-07-09 0:26 ` possible bug with commit-graph causing git to fork bomb (was Re: [External Mail]Re: Git fork process infinitely and never stop) Carlo Marcelo Arenas Belón
2022-07-09 0:52 ` Han Xin
2022-07-09 6:39 ` Carlo Arenas
2022-07-11 4:11 ` 程洋
2022-09-27 14:25 ` 程洋
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=8e1d019e-6456-ed05-7d3e-a0c4beeb35fa@gmail.com \
--to=bagasdotme@gmail.com \
--cc=chengyang@xiaomi.com \
--cc=git@vger.kernel.org \
--cc=hehao@xiaomi.com \
--cc=maxin7@xiaomi.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 NNTP newsgroup(s).