git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: GPF in index-pack

From
Shawn Pearce <spearce@spearce.org>
Date
Aug 6, 2006, 02:48 UTC
Message-ID
<20060806024858.GC20565@spearce.org>
In-Reply-To
<9e4733910608051944v5af7e552wd6909b9773dd516e@mail.gmail.com>
Jon Smirl <jonsmirl@gmail.com> wrote:
Show 5 quoted lines
> 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.
Previous: Jon SmirlNext: Jon Smirl
Message 2 of 9 in “Re: GPF in index-pack”
  1. Jon SmirlAug 6, 2006
  2. Shawn PearceAug 6, 2006
  3. Jon SmirlAug 6, 2006
  4. Shawn PearceAug 6, 2006
  5. Jon SmirlAug 6, 2006
  6. Shawn PearceAug 6, 2006
  7. Jon SmirlAug 6, 2006
  8. Jon SmirlAug 6, 2006
  9. Sergey VlasovAug 6, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.