Your message dated Thu, 31 Aug 2023 22:43:43 +1000
with message-id
<CALy8Cw4YxCWY-67PDR=o2s-cygc_u4smd_r4e0fsfz9fng4...@mail.gmail.com>
and subject line Fixed in 4.0.0.
has caused the Debian Bug report #879674,
regarding /bin/ps:ps/display.c:66: please report this bug
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
879674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879674
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: procps
Version: 2:3.3.12-3
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I was running a script for some days, and over time, firefox memory usage
cranked up, I suspect this has led to the situation, where ps has thrown me a
bug.
The exact output which made me write this bug report (I was running multiple
instances of mawk parallelly):
Signal 11 (SEGV) caught by ps (3.3.12).
mawk: could not create a new process (Cannot allocate memory)
/bin/ps:ps/display.c:66: please report this bug
mawk: could not create a new process (Cannot allocate memory)
Signal 11 (SEGV) caught by ps (3.3.12).
mawk: could not create a new process (Cannot allocate memory)
/bin/ps:ps/display.c:66: please report this bug
mawk: could not create a new process (Cannot allocate memory)
I am not sure, if the mawk has anything to do with the ps error, my script was
roughly:
while sleep 1; do
ps | mawk ...
done
Because of the memory issue, I am not even sure if this is really a bug, but
report it anyway, since the output asked me to do so.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages procps depends on:
ii init-system-helpers 1.48
ii libc6 2.24-11+deb9u1
ii libncurses5 6.0+20161126-1+deb9u1
ii libncursesw5 6.0+20161126-1+deb9u1
ii libprocps6 2:3.3.12-3
ii libtinfo5 6.0+20161126-1+deb9u1
ii lsb-base 9.20161125
Versions of packages procps recommends:
ii psmisc 22.21-2.1+b2
procps suggests no packages.
-- Configuration Files:
/etc/sysctl.conf changed:
kernel.dmesg_restrict = 0
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: procps
Version: 2:4.0.0-1
The library was largely refactored in version 4.0.0, I suspect this quirk
got fixed due to a side-effect of fixing other bugs in the library parser.
--- End Message ---
