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

Re: [PATCH 2/2] index-pack: reduce memory usage when the pack has large blobs

From
IKIan Kumlien <pomac@vapor.com>
Date
Feb 26, 2012, 13:28 UTC
Message-ID
<20120226132834.GK9526@pomac.netswarm.net>
In-Reply-To
<CACsJy8Cncs8RYiSB0N20vy9zu2NRTTHpfw3rSfmW64i-4_wxSw@mail.gmail.com>
On Sun, Feb 26, 2012 at 11:10:14AM +0700, Nguyen Thai Ngoc Duy wrote:
Show 9 quoted lines
> On Sun, Feb 26, 2012 at 5:45 AM, Ian Kumlien <pomac@vapor.com> wrote:
> > Actually, i added a backtrace and used addr2line to confirm my
> > suspicion... which is:
> > builtin/index-pack.c:414
> >
> > ie get_data_from_pack...
> 
> That function should only be called when objects are deltified, which
> should _not_ happen for large blobs. What is its caller?
Full backtrace:

for x in 0x536031 0x451b0e 0x452212 0x4523f5 0x452711 0x452799 0x452bbb 0x454344 0x4170d1 0x41726c ; do addr2line $x -e ../git/git ; done git/wrapper.c:41 git/builtin/index-pack.c:414 git/builtin/index-pack.c:588 git/builtin/index-pack.c:625 git/builtin/index-pack.c:679 git/builtin/index-pack.c:694 git/builtin/index-pack.c:805 git/builtin/index-pack.c:1246 git/git.c:308 git/git.c:467

Which means: xmalloc get_data_from_pack get_base_data -- line just after: if (!delta_nr) { resolve_delta find_unresolved_deltas_1 find_unresolved_deltas parse_pack_objects cmd_index_pack [skipping the git.c part]

Btw, i'm running these tests on a 64 bit laptop - since i'm not at work ;) (had to manually limit xmalloc but it triggers at the same point)

Previous: Nguyen Thai Ngoc Duy
Message 11 of 11 in “Skip SHA-1 collision test on "index-pack --verify"”
  1. 1/2 Skip SHA-1 collision test on "index-pack --verify"Nguyễn Thái Ngọc Duy, Feb 24, 2012
  2. 2/2 index-pack: reduce memory usage when the pack has large blobsNguyễn Thái Ngọc Duy, Feb 24, 2012
  3. Ian KumlienFeb 24, 2012
  4. Ian KumlienFeb 24, 2012
  5. Ian KumlienFeb 24, 2012
  6. Ian KumlienFeb 24, 2012
  7. Nguyen Thai Ngoc DuyFeb 25, 2012
  8. Ian KumlienFeb 25, 2012
  9. Ian KumlienFeb 25, 2012
  10. Nguyen Thai Ngoc DuyFeb 26, 2012
  11. Ian KumlienFeb 26, 2012

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.