This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: Andrew Morton <akpm at linux-foundation dot org>
- Cc: Justin Mattock <justinmattock at gmail dot com>, Linux Kernel Mailing List <linux-kernel at vger dot kernel dot org>, gcc at gcc dot gnu dot org, KOSAKI Motohiro <kosaki dot motohiro at jp dot fujitsu dot com>, David Rientjes <rientjes at cs dot washington dot edu>
- Date: Wed, 04 Nov 2009 13:13:17 +0000
- Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
- References: <dd18b0c30911021329g3c99a783n6b0a293240c3312c@mail.gmail.com> <20091103222432.4a94bd8f.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 2 Nov 2009 13:29:29 -0800 Justin Mattock <justinmattock@gmail.com> wrote:
>
>> Hello,
>> I'm not sure how to handle this,
>> while compiling firefox-3.6b1.source
>> I get this with the default compiling options,
>> as well as custom:
>>
>> ...
>>
>> active_anon:2360492kB inactive_anon:590196kB active_file:84kB
>
> 2.8GB of anonymous memory
>
>> [ 532.942508] Free swap = 0kB
>> [ 532.942510] Total swap = 431632kB
>
> 430MB of swap, all used up.
>
> That's a genuine OOM. Something (presumably cc1plus) has consumed
> waaaay too much memory, quite possibly leaked it.
>
> It would help if the oom-killer were to print some information about
> the oom-killed process's memory footprint.
I would think that the quickest way to proceed would be to re-run the
failing compile command under gdb at the command-line and see what it's doing
when the oom killer signals it, wouldn't it? Or turn up the swap until it
doesn't get killed and see what info can be gleaned from the cc1(plus?)
-fmem-report output.
cheers,
DaveK