Gentoo Archives: gentoo-user

From: Michael Mol <mikemol@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] xz memory hungry?
Date: Wed, 22 Aug 2012 21:45:32
Message-Id: CA+czFiC0Udy+VHGhzixKBiRw7eFs88Qq_A56WyzSEA6Mvb2B5Q@mail.gmail.com
In Reply to: Re: [gentoo-user] xz memory hungry? by Jorge Almeida
1 On Wed, Aug 22, 2012 at 5:16 PM, Jorge Almeida <jjalmeida@×××××.com> wrote:
2 > On Wed, Aug 22, 2012 at 9:39 PM, Florian Philipp <lists@×××××××××××.net> wrote:
3 >> Am 22.08.2012 20:52, schrieb Jorge Almeida:
4 >>
5 >> This should not happen, especially on such a small archive. I've tried
6 >> `strace xz -t m4-1.4.16.tar.xz` and looked for calls to mmap (e.g.
7 >> memory allocations). They never were larger than 68 MB
8 >>
9 >> Try it yourself. The second parameter in mmap is the allocated size in byte.
10 >>
11 >>
12 > In the box where it works:
13
14 [snip]
15 > In the other box, in the gentoo chroot:
16 >
17 > # strace -e trace=mmap2 xz -t /usr/portage/distfiles/m4-1.4.16.tar.xz
18
19 [snip]
20
21 > mmap2(NULL, 67112960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
22 > -1, 0) = -1 ENOMEM (Cannot allocate memory)
23
24 It's only asking for about 65MB of RAM there. ENOMEM is nearly a
25 catch-all failure code for mmap().
26
27 My bet is that it's an incompatibility between the Arch kernel and the
28 version of glibc in the chroot.
29
30 --
31 :wq

Replies

Subject Author
Re: [gentoo-user] xz memory hungry? Michael Mol <mikemol@×××××.com>
Re: [gentoo-user] xz memory hungry? Jorge Almeida <jjalmeida@×××××.com>