It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Push fails with error: pack-objects died of signal 13

I've setup a new repository and I'm trying to push my project to it, but it keeps failing:

git push -u origin --all --verbose
Pushing to
Counting objects: 54942, done.
Delta compression using up to 2 threads.
Connection to closed by remote host.
fatal: The remote end hung up unexpectedly
Compressing objects: 100% (39693/39693), done.
error: pack-objects died of signal 13
error: failed to push some refs to ''



2 answers

1 accepted

0 votes
Answer accepted

Hi Tom!

This repo is well in excess of our size limits. We don't store repositories of this size. We do not offer that as an option to any of our commercial plans, either. 1GiB/2GiB is a firm and inflexible limit for everyone.

As much as we want to offer larger repos, the performance of repos over 750MiB or so is too bad to tolerate. We hope you understand this limitation.

To check this I was asked to run: git count-objects -Hv

Hi @Tom Isaacson,

does this help:

It could be associated with a big file you are trying to push.

I saw that question but the answer refers to the "new GitHub limits on file sizes" so I didn't think it was directly relevant. Does Bitbucket have a limit on file size? If so, why doesn't it give a better error message (as that answer suggests Github is supposed to).

Too be sure that this causes the problem, you can try only pushing a little file. I agree that if this is the problem, the error message is not useful.

Git may not provide a way for Bitbucket to send a better error message. That said, if there is a maximum file size, it ought to be publicly documented somewhere easy to find, like in a FAQ that mentions the error message you're getting.

@Seth Github says they provide a warning about filesize so this must be possible I can't find a file limit for Bitbucket but there is a repository size limit

If this is a persistent problem, you'll probably have to take it up with Bitbucket support.

Hey guys! This is always best worked out with support because we can get into private details like the repository name and such. For what it's worth, we really wish we had a file size limit or overall push limit, but things like that take time to implement and we'd rather refactor push requests or tackle repository organization. Tom has filed a support issue, and we'll let everyone know how it works out here so future people can understand how to resolve it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Atlassian supported Jenkins integration for Bitbucket Server

We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...

939 views 1 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you