Hi Jack,
I’m the guy that added the readproc code you found suspect.
Please don't think of those buffers as representing a memory leak.
Instead, think of them as being statically allocated like this:
#define MAX_BUFSZ 1024*64*2
static char src_buffer[MAX_BUFSZ],
dst_buffer[MAX_BUF
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
Sorry, I should have CC'd this email at the time of sending.
Begin forwarded message:
> From: Jim Warner
> Subject: Re: [amos...@gmail.com: Bug#706259: top crashes due to SEGV]
> Date: April 29, 2013 8:34:56 AM CDT
> To: amos...@gmail.com
> Cc: Craig
Hi Pierre,
I wanted to let you know that with a soon to be released procps-ng-3.3.8 the
top %CPU and %MEM columns will be returned to their former widths and
precision. With yours as the most recent objection, I became convinced that
idea was *not* one of my best.
As for the actual memory col
Lucas,
Thank you for spotting this this bug.
I'm sorry to say that I am the culprit responsible for it.
The top program will soon be fixed in our git repository which can be
found here:
http://gitorious.org/procps
Regards,
Jim
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.de
I'm going to side with the requester, not Craig, on this one.
Jidanni, how do you feel about something like this:
GiB Mem: ... 1.941 used,3.786 free,0.178 buffers
GiB Swap: ... 0.000 used,8.456 free.0.944 cached Mem
Notice the period then the added 'Mem'.
--
To UNSUBSCRIBE, e
Forwarded Message
> From: jida...@jidanni.org
> To: james.war...@comcast.net
> Subject: Re: [Fwd: Re: Bug#718670: top: don't just use comma on second
> line]
> Date: Sat, 10 Aug 2013 05:50:42 +0800
>
> >>>>> "JW" == Jim Warner
Hi Thorsten,
My heart sank a bit when I read your bug report.
When I introduced the new graphs modes I had no intention of altering top’s
behavior for those users with a previously saved rcfile. Unfortunately, my
implementation was a bit short of that goal.
There should soon be a patch availa
Hi Thorsten (again),
An afterthought.
Older tops will not be able to read a 3.3.10 rcfile.
Therefore, your only solution will likely be the patch I mentioned.
Regards,
Jim
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Hi Antti,
The behavior you describe has not changed for over a decade.
That 'z' has always been window specific, affecting just a single window.
It’s documented in the man page under 4c. Task-Area-Commands.
What has changed are the startup defaults in the absence of a previously
saved rcfile. T
On Tue, 27 Jun 2017 19:42:51 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
wrote:
Package: procps
Version: 2:3.3.12-3
Severity: minor
File: /usr/bin/top
It turns out that
$ top
prints trailing blanks all the way to the right edge of the screen.
The problem is gone in -b batch mode, but in intera
Hi Guys,
For what it's worth, I am unable to duplicate the meminfo problem in a
newly created debian-bookworm based lxc container.
I'm using the snap version of lxd identified as:
$ lxc --version
5.21.1 LTS
The top, ps and free programs (all identified as from procps-ng 4.0.2)
work j
On 6/12/24 9:35 AM, Jim Warner wrote:
For what it's worth, I am unable to duplicate the meminfo problem in a
newly created debian-bookworm based lxc container.
I'm using the snap version of lxd identified as:
$ lxc --version
5.21.1 LTS
The top, ps and free programs (all
On Tue, 2 Mar 2021 07:31:33 +1100 Craig Small wrote:
The lxc folks love changing the name of the cgroup on us so I suspect this
has happened (yet) again. The various names procps uses can be found at [1]
Can you pick one process you expect to see the lxc output for and send me
the output of /p
Hi Michael,
That 'yyy' task is not the only out-of-order task.
The 2nd task shown would be misplaced if sorting on TIME+.
However, it looks to me that this sort was on %CPU.
Regards,
Jim
Hi Roman,
We discovered three potential instances of %Cpu distortion in release 4.0.2.
They were all fixed in release 4.0.4, which is available in trixie.
If you could try that package and report back it would be appreciated.
Thanks in advance.
Regards,
Jim
Hi Tim,
There were a series of changes to top key handling in release 4.0.1
prompted by the new 'bottom window' feature (^G, ^N, etc).
Unfortunately, they adversely impacted screen refresh.
That was corrected in release 4.0.4, essentially restoring the former
3.3.17 behavior.
Regards,
Jim
17 matches
Mail list logo
