Hi All,
I’m going to try to put this bug to rest, once and for all.
The top memory leak was serious, but top was a victim, not the culprit.
A fuller explanation can be found in message #27, which unfortunately is
not line wrapped thus making it more difficult to read. So I’ll summarize
here:
1
reopen 627257
thankyou
On Fri, May 18, 2012 at 04:17:03PM +0200, Witold Baryluk wrote:
> I do not know if bug is sitll reproductible with newer version of top,
> but it was previously the case. I cannot reproduce it in this moment,
> but will try with different top configuration.
Unfortunately I go
ay 2012 07:23:57 +1000
From: Craig Small
To: 627257-d...@bugs.debian.org
Subject: [james.war...@comcast.net: [procps] bug #627257, top: memory leaks]
Message-ID: <20120517212356.ga19...@enc.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Conten
Package: procps
Version: 1:3.2.8-10
Severity: important
Hi,
I today noticed that in top, that top eats RAM (rss),
and it incresses. About +8kB per refresh.
It started from about 1MB, and after few minutes
I got 13MB, and it was still climbing.
valgrind also warns me that there are some still rea
4 matches
Mail list logo
