549908 – High memory usage of emerge, memory never freed

Bug 549908 - High memory usage of emerge, memory never freed

Summary: High memory usage of emerge, memory never freed

Status:	RESOLVED DUPLICATE of bug 549906

Alias:	None

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

Importance:	Normal normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2015-05-19 16:10 UTC by .
Modified:	2015-05-19 16:16 UTC (History)
CC List:	0 users

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 . 2015-05-19 16:10:56 UTC

Even with single-package-installs, emerge consumes ~200MB of RSS. World update then needs ~600MB. This memory is also never released and occupies memory until emerge dies.

My laptop has "only" 8GB of memory and during compilation every MB counts.

Reproducible: Always

Steps to Reproduce:
1. emerge some/package OR emerge -uDN @world
2. observe memory usage
3.


Expected Results:  
I'd like to see a big drop in emerge's memory usage as soon as installation begins

Portage 2.2.18 (python 2.7.9-final-0, default/linux/amd64/13.0/desktop, gcc-4.9.2, glibc-2.20-r2, 3.18.13-gentoo x86_64)

Comment 1 Brian Evans (RETIRED) gentoo-dev

2015-05-19 16:16:40 UTC


*** This bug has been marked as a duplicate of bug 549906 ***