Why does Git Clone Fails Even with small repositories?
I have checked a few questions around this area. It seems malloc fail for insufficient memory is a common issue for massive files, and there are some work-arounds.
But my repository size (containing a readme, a few shell scripts, python scripts and config files, all texts), as reported by GitLab is 19.4 MB. When I run
git clone https://gitlab.com/username/project.git
the terminal echoes
fatal: Out of memory, malloc failed (tried to allocate 1744830464 bytes)
which is about 1.5GB. Where do these things come from? Not only I need a work-arounds, but I am also curious whether there is any hidden content in my repository which interferes with a smooth cloning. Also, so far it is a pretty fresh project and I only have one branch.
Using git version 2.19.0.windows.1 on windows 7
But the error does not show up on Linux staging clusters or even in Linux laptops using same configuration. From some further research, it seems the error might have something to do with editing file permissions on my Linux copy, and setting core.filemode to true. I did it because I do have to frequently alter the permissions of files in the production server and wanted these changes to be reflected in the repository.
git version-control gitlab git-clone cloning
asked Nov 26 '18 at 2:54
DellaDella
203214
add a comment |
I have checked a few questions around this area. It seems malloc fail for insufficient memory is a common issue for massive files, and there are some work-arounds.
But my repository size (containing a readme, a few shell scripts, python scripts and config files, all texts), as reported by GitLab is 19.4 MB. When I run
git clone https://gitlab.com/username/project.git
the terminal echoes
fatal: Out of memory, malloc failed (tried to allocate 1744830464 bytes)
which is about 1.5GB. Where do these things come from? Not only I need a work-arounds, but I am also curious whether there is any hidden content in my repository which interferes with a smooth cloning. Also, so far it is a pretty fresh project and I only have one branch.
Using git version 2.19.0.windows.1 on windows 7
But the error does not show up on Linux staging clusters or even in Linux laptops using same configuration. From some further research, it seems the error might have something to do with editing file permissions on my Linux copy, and setting core.filemode to true. I did it because I do have to frequently alter the permissions of files in the production server and wanted these changes to be reflected in the repository.
git version-control gitlab git-clone cloning
asked Nov 26 '18 at 2:54
DellaDella
203214
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32
add a comment |
I have checked a few questions around this area. It seems malloc fail for insufficient memory is a common issue for massive files, and there are some work-arounds.
But my repository size (containing a readme, a few shell scripts, python scripts and config files, all texts), as reported by GitLab is 19.4 MB. When I run
git clone https://gitlab.com/username/project.git
the terminal echoes
fatal: Out of memory, malloc failed (tried to allocate 1744830464 bytes)
which is about 1.5GB. Where do these things come from? Not only I need a work-arounds, but I am also curious whether there is any hidden content in my repository which interferes with a smooth cloning. Also, so far it is a pretty fresh project and I only have one branch.
Using git version 2.19.0.windows.1 on windows 7
But the error does not show up on Linux staging clusters or even in Linux laptops using same configuration. From some further research, it seems the error might have something to do with editing file permissions on my Linux copy, and setting core.filemode to true. I did it because I do have to frequently alter the permissions of files in the production server and wanted these changes to be reflected in the repository.
git version-control gitlab git-clone cloning
asked Nov 26 '18 at 2:54
DellaDella
203214
I have checked a few questions around this area. It seems malloc fail for insufficient memory is a common issue for massive files, and there are some work-arounds.
But my repository size (containing a readme, a few shell scripts, python scripts and config files, all texts), as reported by GitLab is 19.4 MB. When I run
git clone https://gitlab.com/username/project.git
the terminal echoes
fatal: Out of memory, malloc failed (tried to allocate 1744830464 bytes)
which is about 1.5GB. Where do these things come from? Not only I need a work-arounds, but I am also curious whether there is any hidden content in my repository which interferes with a smooth cloning. Also, so far it is a pretty fresh project and I only have one branch.
Using git version 2.19.0.windows.1 on windows 7
But the error does not show up on Linux staging clusters or even in Linux laptops using same configuration. From some further research, it seems the error might have something to do with editing file permissions on my Linux copy, and setting core.filemode to true. I did it because I do have to frequently alter the permissions of files in the production server and wanted these changes to be reflected in the repository.
git version-control gitlab git-clone cloning
git version-control gitlab git-clone cloning
asked Nov 26 '18 at 2:54
DellaDella
203214
asked Nov 26 '18 at 2:54
DellaDella
203214
edited Nov 26 '18 at 6:14
Della
asked Nov 26 '18 at 2:54
DellaDella
203214
asked Nov 26 '18 at 2:54
DellaDella
203214
asked Nov 26 '18 at 2:54
DellaDella
203214
203214
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32
add a comment |
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53474206%2fwhy-does-git-clone-fails-even-with-small-repositories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53474206%2fwhy-does-git-clone-fails-even-with-small-repositories%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is your OS and git version?
– VonC
Nov 26 '18 at 5:48
The on giving the problem is running windows 7 git version 2.19. I added some further information in the question.
– Della
Nov 26 '18 at 6:15
Can you check with Git 2.19.2 or Git 2.20-rc0?
– VonC
Nov 26 '18 at 6:21
Have you tried this one? i.e. git config pack.windowMemory 50m
– ik1ne
Nov 26 '18 at 7:30
The Windows PC is from my company and without any admin privilege. So it is a lot of hassle to do even simple things, such as wiping and re-installing Git etc. Anyway, the problem started after I set core.filemode to true. I have reset it back and also set http.postbuffer=5m, according to some advice. I am not sure about the implications, but now the problem is gone.
– Della
Nov 26 '18 at 7:32