Re: [gentoo-user] xz memory hungry?

[Michael Mol <mikemol@gmail.com>]

On Wed, Aug 22, 2012 at 5:42 PM, Michael Mol <mikemol@gmail.com> wrote:
> On Wed, Aug 22, 2012 at 5:16 PM, Jorge Almeida <jjalmeida@gmail.com> wrote:
>> On Wed, Aug 22, 2012 at 9:39 PM, Florian Philipp <lists@binarywings.net> wrote:
>>> Am 22.08.2012 20:52, schrieb Jorge Almeida:
>>>
>>> This should not happen, especially on such a small archive. I've tried
>>> `strace xz -t m4-1.4.16.tar.xz` and looked for calls to mmap (e.g.
>>> memory allocations). They never were larger than 68 MB
>>>
>>> Try it yourself. The second parameter in mmap is the allocated size in byte.
>>>
>>>
>> In the box where it works:
>
> [snip]
>> In the other box, in the gentoo chroot:
>>
>> # strace -e trace=mmap2 xz -t /usr/portage/distfiles/m4-1.4.16.tar.xz
>
> [snip]
>
>> mmap2(NULL, 67112960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
>> -1, 0) = -1 ENOMEM (Cannot allocate memory)
>
> It's only asking for about 65MB of RAM there. ENOMEM is nearly a
> catch-all failure code for mmap().
>
> My bet is that it's an incompatibility between the Arch kernel and the
> version of glibc in the chroot.

(incidentally...hey! It's Gentoo-related after all. ;) )

-- 
:wq