Your message dated Sun, 17 Mar 2002 13:00:46 -0700 (MST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#138692: apt-get uses an enormous amount of memory for
simple functions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Mar 2002 04:19:28 +0000
>From [EMAIL PROTECTED] Sat Mar 16 22:19:28 2002
Return-path: <[EMAIL PROTECTED]>
Received: from bgp526611bgs.ebrnsw01.nj.comcast.net (kahuna.ns) [68.38.83.114]
(foobar)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16mS8m-0004zA-00; Sat, 16 Mar 2002 22:19:28 -0600
Received: from darth.ns (darth.ns [192.168.1.40])
by kahuna.ns (8.12.2/8.12.2/Debian -4) with ESMTP id g2H4JPVJ020496;
Sat, 16 Mar 2002 23:19:26 -0500
Received: from compwiz by darth.ns with local (Exim 3.35 #1 (Debian))
id 16mS8j-0003Jv-00; Sat, 16 Mar 2002 23:19:25 -0500
From: Ari Pollak <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: apt-get uses an enormous amount of memory for simple functions
X-Mailer: reportbug 1.48
Date: Sat, 16 Mar 2002 23:19:25 -0500
Message-Id: <[EMAIL PROTECTED]>
Sender: Ari Pollak <[EMAIL PROTECTED]>
X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/)
Delivered-To: [EMAIL PROTECTED]
Package: apt
Version: 0.5.4
Severity: normal
When I do an 'apt-get source libgtk1.2', the apt-get process seems to
use 100+ MB of RAM until the extraction is over. Consequently, this
slows my system down a lot. Here is a line from ps aux when apt-get
source is running:
compwiz 12696 2.8 39.1 104416 100644 pts/8 S 23:16 0:00 apt-get source li
compwiz 12728 0.0 39.1 104416 100648 pts/8 S 23:17 0:00 apt-get source li
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux darth 2.4.19-pre3 #1 Tue Mar 12 20:38:26 EST 2002 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages apt depends on:
ii libc6 2.2.5-3 GNU C Library: Shared libraries an
ii libstdc++2.10-glibc2.2 1:2.95.4-4 The GNU stdc++ library
---------------------------------------
Received: (at 138692-done) by bugs.debian.org; 17 Mar 2002 20:00:49 +0000
>From [EMAIL PROTECTED] Sun Mar 17 14:00:49 2002
Return-path: <[EMAIL PROTECTED]>
Received: from crack-ext.ab.videon.ca [206.75.216.33]
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 16mgpl-0003rQ-00; Sun, 17 Mar 2002 14:00:49 -0600
Received: (qmail 6034 invoked from network); 17 Mar 2002 20:00:47 -0000
Received: from unknown (HELO wakko.debian.net) ([24.86.210.128])
(envelope-sender <[EMAIL PROTECTED]>)
by crack-ext.ab.videon.ca (qmail-ldap-1.03) with SMTP
for <[EMAIL PROTECTED]>; 17 Mar 2002 20:00:47 -0000
Received: from localhost
([127.0.0.1] helo=wakko.debian.net ident=jgg)
by wakko.debian.net with smtp (Exim 3.16 #1 (Debian))
id 16mgpi-0007r8-00; Sun, 17 Mar 2002 13:00:46 -0700
Date: Sun, 17 Mar 2002 13:00:46 -0700 (MST)
From: Jason Gunthorpe <[EMAIL PROTECTED]>
X-Sender: [EMAIL PROTECTED]
To: Ari Pollak <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
cc: APT Development Team <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#138692: apt-get uses an enormous amount of memory for simple
functions
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
On Sat, 16 Mar 2002, Ari Pollak wrote:
> When I do an 'apt-get source libgtk1.2', the apt-get process seems to
> use 100+ MB of RAM until the extraction is over. Consequently, this
> slows my system down a lot. Here is a line from ps aux when apt-get
> source is running:
Well, I can't reproduce this, and nobody else has ever reported it. I'm
afraid you are going to have to find out what is wrong with your system on
your own and then file a bug.
Jason
