public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Justin Mattock <justinmattock@gmail.com>,
	  Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 gcc@gcc.gnu.org,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	  David Rientjes <rientjes@cs.washington.edu>
Subject: Re: cc1plus invoked oom-killer: gfp_mask=0x280da, order=0,  oom_adj=0
Date: Wed, 04 Nov 2009 12:58:00 -0000	[thread overview]
Message-ID: <4AF17DED.7080808@gmail.com> (raw)
In-Reply-To: <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

  parent reply	other threads:[~2009-11-04 12:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 21:29 Justin Mattock
2009-11-02 21:49 ` Jiri Slaby
2009-11-02 22:02   ` Justin Mattock
2009-11-02 22:05     ` Jiri Slaby
2009-11-02 22:12       ` Justin P. Mattock
2009-11-03  0:56       ` Justin P. Mattock
2009-11-04  1:18 ` KOSAKI Motohiro
2009-11-04  1:40   ` Justin P. Mattock
2009-11-04  6:24 ` Andrew Morton
2009-11-04  6:44   ` Justin P. Mattock
2009-11-04  9:14     ` Jiri Slaby
2009-11-04  9:32   ` KOSAKI Motohiro
2009-11-04 15:29     ` Andrew Morton
2009-11-04 23:20       ` KOSAKI Motohiro
2009-11-04 12:58   ` Dave Korn [this message]
2009-11-04 15:08     ` Justin P. Mattock
2009-11-04 15:30       ` Dave Korn
2009-11-04 16:40         ` Justin Mattock
2009-11-04 19:33           ` Dave Korn
2009-11-04 20:39             ` Justin P. Mattock
2009-11-04 21:22               ` Justin Mattock
2009-11-05  0:21                 ` Dave Korn
2009-11-05  3:36                   ` Justin Mattock
2009-11-05  4:53                     ` Dave Korn
2009-11-06 21:21                       ` Justin P. Mattock
2009-11-10  2:55                       ` Justin P. Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF17DED.7080808@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=gcc@gcc.gnu.org \
    --cc=justinmattock@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rientjes@cs.washington.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).