libgit2 / libgit2/libgit2sharp
"Out of memory" LibGit2SharpException thrown when attempting to clone using Repository.Clone(...)
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
Reproduction steps
- Create a repo.
- Add some large files (>700 MB).
- Move the large files and author a commit.
- Attempt to clone the repo using Repository.Clone(...)
- Observe that a LibGit2SharpException is thrown with a message that states "Out of memory".
Expected behavior
- Create a repo.
- Add some large files (>700 MB).
- Move the large files and author a commit.
- Attempt to clone the repo using Repository.Clone(...)
- Clone succeeds without throwing an exception.
Actual behavior
- Create a repo.
- Add some large files (>700 MB).
- Move the large files and author a commit.
- Attempt to clone the repo using Repository.Clone(...)
- Observe that a LibGit2SharpException is thrown with a message that states "Out of memory".
Version of LibGit2Sharp (release number or SHA1)
0.27.0-preview-0175
Operating system(s) tested; .NET runtime tested
.NET Framework 4.6.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with a repository containing moved files larger than 700 MB, using Repository.Clone(...) on .NET Framework 4.6.1. Start by examining the LibGit2SharpException reporting "Out of memory" during the clone. Done means the same repository clones successfully without throwing that exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100