Bug 922465 - ps: failed to allocate 1220640768 bytes of memory
Summary: ps: failed to allocate 1220640768 bytes of memory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: procps-ng
Version: 18
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-17 08:37 UTC by Jan ONDREJ
Modified: 2016-02-01 01:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-31 17:50:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
strace log (46.42 KB, text/x-log)
2013-03-17 08:37 UTC, Jan ONDREJ
no flags Details
/proc/PID/status (3.73 KB, text/plain)
2013-03-17 08:37 UTC, Jan ONDREJ
no flags Details

Description Jan ONDREJ 2013-03-17 08:37:11 UTC
Created attachment 711283 [details]
strace log

Description of problem:
On an 32-bit system, ps process is trying to allocate 3 GB of RAM.

Version-Release number of selected component (if applicable):
kernel-PAE-3.8.2-206.fc18.i686
procps-ng-3.3.3-2.20120807git.fc18.i686
glibc-2.16-28.fc18.i686

How reproducible:
90%

Steps to Reproduce:
1. ps
  
Actual results:
�1�H]o>���H ��H failed to allocate 1220640768 bytes of memory[root.sk ~]# 

Expected results:
process list

Additional info:
Using "ps x" will display some processes. Looks like it's failing on 2nd process of httpd. Possible problem is with process which has too many groups. Strace and the /proc/PID/status file are attached.
Possible same problem is on 64bit system, but allocating 3 GB on 64bit is possible, but can affect systems with small RAM.

Comment 1 Jan ONDREJ 2013-03-17 08:37:40 UTC
Created attachment 711284 [details]
/proc/PID/status

Comment 2 Jan ONDREJ 2013-04-02 11:35:37 UTC
Some service startup scripts are using ps during startup process, which fails to start/stop some services at boot. Please, fix this bug.
For example apache fails to start at aprox. 50% of attempts.

Comment 3 Jaromír Cápík 2013-05-16 13:37:25 UTC
Hello Jan.

Could you please test the latest version available in f19 or rawhide?

The RPMs can be downloaded from here:
http://koji.fedoraproject.org/koji/buildinfo?buildID=412140

Please, let me know.

Thank you.

Regards,
Jaromir.

Comment 4 Jan ONDREJ 2013-05-17 05:46:37 UTC
Hello,

(In reply to comment #3)
> Could you please test the latest version available in f19 or rawhide?

I can't test it, because I can't reproduce this with current F18. My current packages:

kernel-PAE-3.8.5-201.fc18.i686
procps-ng-3.3.3-4.20120807git.fc18.i686
glibc-2.16-31.fc18.i686

Is it possible, that procps-ng-3.3.3-4 fixed this bug?

* Po mar 04 2013 Jaromir Capik <jcapik> - 3.3.3-3.20120807git
- Fixing ps crashes caused by insufficient buffer sizes (#917705)

Comment 5 Fedora End Of Life 2013-12-21 12:13:19 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Jaromír Cápík 2014-01-31 17:50:37 UTC
Hello Jan.

Sorry for no reply. Yes, it was very probably caused by the already resolved insufficient buffer size.
I'm closing this report as you were unable to reproduce the problem with the latest updates.
Anyway, if the problem appears again, do not hesitate to reopen this bug.

Thanks for the report.

Regards,
Jaromir.


Note You need to log in before you can comment on or make changes to this bug.