git push fatal: unable to create thread: Resource temporarily unavailable

GitGit Push

Git Problem Overview


I'm new to git. I'm want to push a large commit to a remote server but the problem is when I use

git push origin master

it return the error

Counting objects: 5009, done.
Delta compression using up to 16 threads.
fatal: unable to create thread: Resource temporarily unavailable
error: pack-objects died with strange error

So is there anyway I can set the max thread use for Delta Compression.

Thanks for help,

Yuan Chen

Git Solutions


Solution 1 - Git

The error: "fatal: unable to create thread: Resource temporarily unavailable" strongly suggests you've run out of memory on the server, which can happen if you have a repository with lots of large files, which can cause re-packing to take a lot of memory, or limited virtual memory - either in general, or just for that account due to the ulimit setting.

Anyways, here's the commands you can run to limit the amount of memory that packing may take by logging into the remote system (as the user that git runs as) and typing these commands:

git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"
git config --global pack.threads "1"

Hope this works.

Solution 2 - Git

In shared hosting we have limited cpu resources mostly 1 cpu so multi-threading does not work very well there. This error is due to limited cpu resource actually.

Just this one git setting is enough to resolve this.

git config --global pack.threads "1"

This is limiting git to create only one thread.

Solution 3 - Git

I've also stumbled upon this error. To make it simpler, this error occurs because you want to copy a 100mb file into a hdd with free space of 50mb (or less). To fix this, SSH into the server and run the following commands:

git config --global pack.windowMemory "100m"
git config --global pack.packSizeLimit "100m"

Solution 4 - Git

"unable to create thread: Resource temporarily unavailable" means an issue with the remote server (like no more memory available).

Regarding delta, you have the following config to tweak:

pack.deltaCacheSize

> The maximum memory in bytes used for caching deltas in git-pack-objects(1) before writing them out to a pack.
This cache is used to speed up the writing object phase by not having to recompute the final delta result once the best match for all objects is found.
Repacking large repositories on machines which are tight with memory might be badly impacted by this though, especially if this cache pushes the system into swapping.
A value of 0 means no limit.
The smallest size of 1 byte may be used to virtually disable this cache. Defaults to 256 MiB.

pack.deltaCacheLimit

> The maximum size of a delta, that is cached in git-pack-objects(1).
This cache is used to speed up the writing object phase by not having to recompute the final delta result once the best match for all objects is found. Defaults to 1000.

The SO question "Git pull fails with bad pack header error" references other pack-related configs.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionYuan ChenView Question on Stackoverflow
Solution 1 - GitWaqarView Answer on Stackoverflow
Solution 2 - GitMuzaffar MahmoodView Answer on Stackoverflow
Solution 3 - GitNguyen KienView Answer on Stackoverflow
Solution 4 - GitVonCView Answer on Stackoverflow