mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

close as dup

Browse source
This commit is contained in:
Joey Hess 2017-06-09 13:43:53 -04:00
parent aa2ab14a83
commit 99a1e6efe2
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/Out_of_memory_error_when_adding_large_files_to_v6_repository.mdwn
View file

@ -53,3 +53,5 @@ I have no idea why it needs to do that, though.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
I've been using git-annex v5 repositories without any issues, and with smaller files, repository v6 works great!
> dup; [[done]] --[[Joey]]

19
doc/bugs/Out_of_memory_error_when_adding_large_files_to_v6_repository/comment_1_b9154c38406fca40c4c0edb716707c3a._comment Normal file
View file

@ -0,0 +1,19 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-06-09T17:34:40Z"
content="""
Unfortunately, git add tries to load the whole file content
into memory (or at least allocates a buffer for it all),
even if it's only going to stream it through the clean filter
used in v6 mode, and even though the git-annex smudge
filter reads the file content from disk itself.
I submitted a patch to git over a year ago, that IIRC fixes this kind of
problem, but it was not accepted. Getting an updated version of that patch
accepted into git is the main blocker for v6 repositories to not be
experimental.
[[todo/smudge]] documents this problem. I'm going to close this bug
as it's a duplicate of stuff discussed there.
"""]]