5817 – portage 2.0.22 OOM killed

Bug 5817 - portage 2.0.22 OOM killed

Summary: portage 2.0.22 OOM killed

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High major (vote)
Assignee:	Kevyn Shortell (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-31 08:35 UTC by Spider (RETIRED)
Modified:	2011-10-30 22:19 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Spider (RETIRED) gentoo-dev

2002-07-31 08:35:05 UTC

I attempted to update my older 2.95.3 system, mounted it up and chrooted, emerge
portage (need latest or it will crash at mozilla) and then *blamm*

emerge -pu world will get killed by OOM killer once ebuild.sh has >1GB of ram
allocated.

25102 root      16   0  794M 192M   860 R    33.2 68.5   1:04 ebuild.sh
24880 root      10   0  286M  35M   504 S    11.8 12.7   0:26 python2.2

and a bit later
25102 root      11   0 1101M 228M   856 D    29.3 81.2   1:27 ebuild.sh



Darkmere / # emerge -pu world

These are the packages that I would merge, in order.

Terminated


This should be considered... bug.

I'll compress my var/db/pkg and /var/cache for you

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-08-01 01:35:42 UTC

If you can faithfully reproduce this, I'll need to ssh into your box.  Can't
reproduce it here.

Comment 2 Daniel Ahlberg (RETIRED) gentoo-dev

2002-08-01 16:10:05 UTC

I get this too when trying to run two emerge's at the same time. What info do
you need to track this down?

Comment 3 Daniel Robbins (RETIRED) gentoo-dev

2002-08-04 21:18:54 UTC

fix in 2.0.24

Comment 4 Nicholas Jones (RETIRED) gentoo-dev

2002-10-13 14:50:09 UTC

Old. Fixed. Closed.