Re: JVM Memory leak on unpack error in Gerrit 2.1.8

405 views
Skip to first unread message

Shawn Pearce

unread,
Aug 2, 2012, 1:39:38 PM8/2/12
to Dom Alessi, repo-d...@googlegroups.com
On Thu, Aug 2, 2012 at 7:21 AM, Dom Alessi <doma...@gmail.com> wrote:
> We currently have a repo on our gerrit 2.1.8 instance that is causing the
> JVM Heap to be exhausted. The error the user gets is the following when
> doing a push:
>
>>> remote: Resolving deltas: 24% (763/3179)
>>> remote: Resolving deltas: 25% (795/3179)
>>> remote: Resolving deltas: 26% (836/3179)
>>> remote: Resolving deltas: 26% (840/3179)
>>>
>>> error: unpack failed: error Out of memory loading unknown object
>>> fatal: Unpack error, check server log To
>>> ssh://username@server:29418/ipos_git_lite_gerrit_pilot-sfi
>>> ! [remote rejected] master -> swfeature_int.git-master (n/a
>>> (unpacker error))
>>> error: failed to push some refs to
>>> 'ssh://username@server:29418/ipos_git_lite_gerrit_pilot-sfi'

Are you pushing a file that is >2G in size? Or something equally large
that is say 800M and the JVM just can't allocate an 800M contiguous
block of memory?

Dom Alessi

unread,
Aug 8, 2012, 10:14:59 AM8/8/12
to repo-d...@googlegroups.com
It seems as though, I was lucky on my push.  We tried from different client locations and get different results.  If anyone can provide an insight on how to proceed it would be great.  Again, the push really only has a text file that had a large number of diffs in 1 commit and nothing else.

BR,
Dom

On Thu, Aug 2, 2012 at 3:31 PM, Dom Alessi <doma...@gmail.com> wrote:
Hi Shawn,

The user is pushing a 300 MB ascii file.  At first I thought it may have been a really large binary file. We have had some users commit 1 GB files with no issue (not saying it a good thing), but never had an issue. We have since resolved the issue, but not sure if it was because of our action.  We performed a git gc on that repo directly on the server and then I create a clone directly on the server, applied the user's patch and it seemed to work.  Still a bit weireded out by the memory leak on the Unpack Error though.

BR,
Dom

Reply all
Reply to author
Forward
0 new messages