[Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
Sven Hartrumpf
1874824 at bugs.launchpad.net
Fri Oct 23 13:34:21 UTC 2020
Even worse for Ubuntu 20.10 (procps 2:3.3.16-5ubuntu2). With a stack
limit of 500000, almost 11 seconds for a simple pgrep; without
stacklimit, immediate crash.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1874824
Title:
pgrep reports error "cannot allocate" when run without stack limit
Status in procps package in Ubuntu:
Confirmed
Status in procps package in Debian:
New
Bug description:
If you have no stack limit (ulimit -S -s unlimited), any pgrep call
will fail with an error:
> pgrep vim
pgrep: cannot allocate 4611686018427387903 bytes
If you have a high stack limit (e.g. ulimit -S -s 500000), pgrep is
very slow:
> time pgrep vim
2196
real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444
The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152
Archlinux bug report: https://bugs.archlinux.org/task/66093
procps:
Installed: 2:3.3.16-1ubuntu2
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+subscriptions
More information about the foundations-bugs
mailing list