destroycomputers
destroycomputers
I have encountered this, too. A quick run under Instruments showed that in my case the issue was due to multi-pack index validation. The issue only appears after some time...
> It seems the multi-pack index is causing multiple issues - performance issues reported here, and "object not found" issues reported internally ("not found" by libgit2, but found by git)....
@quark-zju is it possible in your build system to compile the dependency statically? Given their (`git2` crate) set up, cargo will compile libgit2 statically unless it finds a dynamic library...
@quark-zju fair enough, thanks for the reply.