git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Memory leak with sparse-checkout

From
CCalbabreaker <calbabreaker@gmail.com>
Date
Sep 20, 2021, 12:15 UTC
Message-ID
<CAKRwm5a9PyqffEC5N__urSpNcZ-d5vz9GBM2Ei16eGS25B=-FQ@mail.gmail.com>
What did you do before the bug happened? (Steps to reproduce your issue)
This was ran:

git clone https://github.com/Calbabreaker/piano --sparse cd piano git sparse-checkout add any_text git checkout deploy-frontend git sparse-checkout init --cone git sparse-checkout add any_text

Basically clone any repository with --sparse, add anything to sparse-checkout list then checkout to another branch, init the sparse-checkout with --cone and add anything to it again.

What did you expect to happen? (Expected behavior)
Nothing at all except for the sparse-checkout list to be updated.
What happened instead? (Actual behavior)

A massive memory leak using all the RAM with one of the cpu cores being at 100% usage.

[System Info] git version: git version 2.33.0 cpu: x86_64 no commit associated with this build sizeof-long: 8 sizeof-size_t: 8 shell-path: /bin/sh uname: Linux 5.10.63-1-MANJARO #1 SMP PREEMPT Wed Sep 8 14:13:59 UTC 2021 x86_64 compiler info: gnuc: 11.1 libc info: glibc: 2.33 $SHELL (typically, interactive shell): /usr/bin/zsh

Next: Taylor Blau
Message 1 of 15 in “Memory leak with sparse-checkout”
  1. CalbabreakerSep 20, 2021
  2. Taylor BlauSep 20, 2021
  3. Derrick StoleeSep 20, 2021
  4. Taylor BlauSep 20, 2021
  5. Derrick StoleeSep 20, 2021
  6. Derrick StoleeSep 20, 2021
  7. Taylor BlauSep 20, 2021
  8. Derrick StoleeSep 20, 2021
  9. Taylor BlauSep 20, 2021
  10. Derrick StoleeSep 21, 2021
  11. Taylor BlauSep 21, 2021
  12. Derrick StoleeSep 21, 2021
  13. Taylor BlauSep 21, 2021
  14. Derrick StoleeSep 22, 2021
  15. Taylor BlauSep 22, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.