git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
* Bug report. Out of memory about git checkout.
@ 2022-06-22 13:55 void f
  0 siblings, 0 replies; 2+ messages in thread
From: void f @ 2022-06-22 13:55 UTC (permalink / raw)
  To: git

—env:

git version: 2.19.1
os : center os
memory 8G

— how to repeat this bug:

Build a repository with large lfs-file use GIT_LFS_SKIP_SMUDGE like
this:  (I can't push a 10G lfs-file to github, So I can’t give you an
example repostiory)

```
hecanwei@MacBook-Pro lfs-test % git st
On branch master
nothing to commit, working tree clean
hecanwei@MacBook-Pro lfs-test % echo "$(cat Xcode_13.4.1.xip )"
version https://git-lfs.github.com/spec/v1
oid sha256:a1e0dbd6d5a96c4a6d3d63600b58486759aa836c2d9f7e8fa6d7da4c7399638b
size 10783587696
```


Rm Xcode_13.4.1.xip

Git checkout .

You will see “Out of memory, realloc failed”

It also use too much memory above version: 2.36.1 macOS


— reason of the bug:


When you execute git checkout, Which have to checkout a lfs-file to
the worktree. Git would execute **convert.c
apply_multi_file_filter()** to convert lfs pointer from git-object to
the lfs file. It will execute a subprocess to convert this file. But
It is strange that git would read all of the file into memory When
finish the git-lfs subprocess. (The code is about pkt-line.c
read_packetized_to_strbut()). Lfs usually is a very large file even
more than the memory. So it would throw out of memory exception.

With this bug, it would have trouble to use sparse-chekout in a
repository with large lfs-file. Because you must init the repository
first and set the sparse-chekout config, than use git
pull/merge/checkout to checkout your subset worktree. It would out of
memory when you checkout it.

I think git don’t need to read all of the file in memory. It can use a
stream to finish the checkout.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Bug report. Out of memory about git checkout.
@ 2022-06-22 13:53 void f
  0 siblings, 0 replies; 2+ messages in thread
From: void f @ 2022-06-22 13:53 UTC (permalink / raw)
  To: git

How to repeat:

env:

git version: 2.36.1
os : center os
memory 8G

When you execute "git checkout .” to chekout a very large lfs-file,
Which is larger than your memory. It would throw “Out of memory,
realloc failed” exception.


reason of the bug:


When you execute git checkout, Which have to checkout a lfs-file to
the worktree. Git would execute "convert.c apply_multi_file_filter()"
to convert lfs pointer from git-object to the lfs file. It will
execute a subprocess to convert this file. But It is strange that git
would read all of the file into memory When finish the git-lfs
subprocess. (The code is about pkt-line.c
read_packetized_to_strbut()). Lfs usually is a very large file even
more than the memory. So it would throw out of memory exception.

With this bug, it would have trouble to use sparse-chekout in a
repository with large lfs-file. Because you must init the repository
first and set the sparse-chekout config, than use git
pull/merge/checkout to checkout your subset worktree. It would out of
memory when you checkout it.

I think git don’t need to read all of the file in memory. It can use a
stream to finish the checkout.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-06-22 13:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-22 13:55 Bug report. Out of memory about git checkout void f
  -- strict thread matches above, loose matches on Subject: below --
2022-06-22 13:53 void f

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).