From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Pearce Subject: Re: GPF in index-pack Date: Sat, 5 Aug 2006 22:48:58 -0400 Message-ID: <20060806024858.GC20565@spearce.org> References: <9e4733910608051805j1192d910hf55393f1dbe1e472@mail.gmail.com> <9e4733910608051944v5af7e552wd6909b9773dd516e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: git X-From: git-owner@vger.kernel.org Sun Aug 06 04:49:11 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G9YhP-000609-Gv for gcvg-git@gmane.org; Sun, 06 Aug 2006 04:49:07 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751493AbWHFCtE (ORCPT ); Sat, 5 Aug 2006 22:49:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751494AbWHFCtE (ORCPT ); Sat, 5 Aug 2006 22:49:04 -0400 Received: from corvette.plexpod.net ([64.38.20.226]:9606 "EHLO corvette.plexpod.net") by vger.kernel.org with ESMTP id S1751493AbWHFCtC (ORCPT ); Sat, 5 Aug 2006 22:49:02 -0400 Received: from cpe-74-70-48-173.nycap.res.rr.com ([74.70.48.173] helo=asimov.home.spearce.org) by corvette.plexpod.net with esmtpa (Exim 4.52) id 1G9Yh6-0005Jj-Ux; Sat, 05 Aug 2006 22:48:49 -0400 Received: by asimov.home.spearce.org (Postfix, from userid 1000) id A2F7C20FB77; Sat, 5 Aug 2006 22:48:58 -0400 (EDT) To: Jon Smirl Content-Disposition: inline In-Reply-To: <9e4733910608051944v5af7e552wd6909b9773dd516e@mail.gmail.com> User-Agent: Mutt/1.5.11 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - corvette.plexpod.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - spearce.org X-Source: X-Source-Args: X-Source-Dir: Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Jon Smirl wrote: > Process size is 2.6GB when the seg fault happen. That's a lot of > memory to build a pack index over 1M objects. > > I'm running a 3:1 process address space split. I wonder why it didn't > grow all the way to 3GB. I still have RAM and swap available. Was the pack you are trying to index built with that fast-import.c I sent last night? Its possible its doing something weird that pack-index can't handle, such as insert a duplicate object into the same pack... How big is the pack file? I'd expect pack-index to be using something around 24 MB of memory (24 bytes/entry) but maybe its hanging onto a lot of data (memory leak?) as it decompresses the entries to compute the checksums. -- Shawn.