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

Re: Out of memory, malloc failed

From
SRSham Rao <sham@styk.net>
Date
May 9, 2009, 00:41 UTC
Message-ID
<loom.20090509T003749-604@post.gmane.org>
In-Reply-To
<4A049715.10407@styk.net>
sham <sham <at> styk.net> writes:
Show 18 quoted lines
> 
> Can anyone shed some light on this?  What can I do to get past this...
> 
> #0  die (err=0x4bfb09 "Out of memory, malloc failed") at usage.c:71
> #1  0x000000000049ac8c in xmalloc (size=555680492) at wrapper.c:29
> #2  0x000000000048e59f in unpack_compressed_entry (p=0x71d690,
> ...Snip...
> #8  0x000000000046b42a in checkout_entry (ce=0x7ffff4d73080,
> state=0x7fffffffdb10, topath=<value optimized out>) at entry.c:233
> #9  0x000000000041488d in cmd_checkout (argc=<value optimized out>,
> argv=<value optimized out>, prefix=0x0) at builtin-checkout.c:141
> #10 0x0000000000404843 in handle_internal_command (argc=2,
> argv=0x7fffffffdde0) at git.c:241
> #11 0x0000000000404a5c in main (argc=2, argv=0x7fffffffdde0) at git.c:481
> 
> Thanks,
> Sham
> 

I was able to resolve this issue by changing limits via the ulimit command. Upon increasing the values using ulimit -m WWWW and ulimit -v XXXX, the git checkout worked (although slow).

-Sham
Previous: sham
Message 2 of 2 in “Out of memory, malloc failed”
  1. shamMay 8, 2009
  2. Sham RaoMay 9, 2009

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.