microsoft / microsoft/VFSForGit
Repeated out-of-memory issues in native Git processes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Several users are hitting this error
"Operation": "TryWriteMultiPackIndex",
"packDir": "XXXX",
"Errors": "fatal: Out of memory, realloc failed\n",
"Output": "",
"ErrorMessage": "fatal: Out of memory, realloc failed\n"
While it doesn't take down mount it can cause degraded performance. We should investigate why it is occurring and see if there is anything we can do.
Example MountIds:
MountIds
2a8c191ce2394b8994be9fa07a05ceed
e10e3781201c4f1fbb0c067f3e2b055d
7a9bc1371a7248e39e8561f649c1bf7e
cd9afd00329342f4959197db0f03dadb
0f96a40f34d84956a8be66da411a8b09
0b2d312140d84bd9b82adc01bc7cf4df
a713e5d6dd3f42a488490c478da680d7
b054f3f74cc347e4a65ca4c337e756b8
Related Error
fatal: Out of memory, malloc failed (tried to allocate 6283720 bytes)
MountIds
a443bd92eeed4c018ec68b07fd897ba4
0f96a40f34d84956a8be66da411a8b09
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
Start with the native Git TryWriteMultiPackIndex operation and correlate the listed MountIds with the malloc and realloc failures. Investigate why these processes exhaust memory, then verify that a mitigation prevents recurrence without causing degraded mount performance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- devtools, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100