>- git version: >2.36.1 >- steps to reproduce the bug >: We have no idea actually. We're maintainer of our internal git/gerrit. We found sometimes some user will invoke 100+ threads to clone the same repository. And when we ask those guy, they say they only executed the "git fetch" once. And just like the youtube videio, you will find git fork a child git, and then grandson child git, and loop like this forever until the server down. >If we copy their local repository to our own PC, and then execute `git fetch`, we can also reproduce it. It seems that some broken local git files cause this bug So the repo "git/gerrit" is hosted in your local? and how you "copy" it to your own PC?
