From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Out of memory error
Date: Sat, 19 Nov 2011 17:04:10 +0000 [thread overview]
Message-ID: <201111191704.29179.michaelkintzios@gmail.com> (raw)
In-Reply-To: <1923565.CFlCjsN4RG@localhost>
[-- Attachment #1: Type: Text/Plain, Size: 2532 bytes --]
On Saturday 19 Nov 2011 15:57:58 Volker Armin Hemmann wrote:
> Am Samstag 19 November 2011, 14:42:07 schrieb Nikos Chantziaras:
> > On 11/19/2011 01:29 PM, Mick wrote:
> > > On Saturday 19 Nov 2011 09:13:33 Nikos Chantziaras wrote:
> > >> On 11/18/2011 07:42 PM, Mick wrote:
> > >>> I've changed the title ever so slightly. I am getting an out of
> > >>> memory
> > >>> error with kernel-2.6.39-gentoo-r3 too, so I can't blame it on the
> > >>> kernel.
> > >>>
> > >>> The error as far as firefox is concerned is the same. Is this a
> > >>> firefox bug, or is my decrepit old laptop incapable of compiling
> > >>> Firefox ...
> > >>>
> > >>> Am I the only one suffering from this?
> > >>
> > >> How much RAM do you have? How big if your swap?
> > >
> > > # free
> > >
> > > total used free shared
> > > buffers cached>
> > >
> > > Mem: 640392 133084 507308 0 81360
> > > 23972
> > > -/+ buffers/cache: 27752 612640
> > > Swap: 257004 6156 250848
> > >
> > > May not be much by today's standards, but I never had an out of memory
> > > error that I can recall just compiling packages in the past.
> >
> > You have 640MB RAM and 256MB swap. That isn't nearly enough to compile
> > big packages nowadays.
> >
> > You can try to increase your swap partition from 256MB to 3GB. However,
> > hitting the swap during a compile is going to strangle your system. To
> > maximize available RAM, logout of the desktop first, then shutdown the
> >
> > graphical environment entirely:
> > /etc/init.d/xdm stop
> >
> > and then compile. Start the desktop again after that:
> > /etc/init.d/xdm start
> >
> > Modern versions of GCC and binutils are quite memory hungry, so your
> > only real option is to add more RAM. You should have at least 2GB of it
> > these days for a Gentoo system.
>
> makeopts -j1 helps too.
Thanks guys.
From your comments it seems that it's been touch & go so far. This is an old
PIII laptop which I have been keeping up to date without any problems until
now. OOo was never emerged on this machine, I have always used ooo-bin. I
did emerge chromium though (early versions) and have not had problems with
gcc.
Perhaps the latest Firefox broke its back. Will try again to emerge it with -
j1 and see if it makes a difference or if that fails I will add a swap file to
give it some breathing space.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-11-19 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 6:53 [gentoo-user] Out of memory error on gentoo kernel 3.0.6 Mick
2011-11-18 17:42 ` [gentoo-user] Re: Out of memory error Mick
2011-11-19 9:13 ` Nikos Chantziaras
2011-11-19 11:29 ` Mick
2011-11-19 12:25 ` Michael Mol
2011-11-19 13:08 ` Pandu Poluan
2011-11-19 17:37 ` Hans Müller
2011-11-20 18:48 ` Mick
2011-11-20 19:31 ` Dale
2011-11-19 12:42 ` Nikos Chantziaras
2011-11-19 15:57 ` Volker Armin Hemmann
2011-11-19 17:04 ` Mick [this message]
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=201111191704.29179.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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