Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling psutil.get_process_list() allocates all the memory on system (FreeBSD) #339

Closed
giampaolo opened this issue May 23, 2014 · 5 comments

Comments

@giampaolo
Copy link
Owner

From [email protected] on November 17, 2012 21:22:31

What steps will reproduce the problem?  
1. Call psutil.get_process_list() (or any other process-related method) on FreeBSD. 

What is the expected output?  
Process list. 

What do you see instead?  
Python allocates all the memory on system and gets killed. 

What version of psutil are you using? What Python version?  
Bug exists in both latest stable (0.6.1) and latest SVN version. 

On what operating system? Is it 32bit or 64bit version?  
Tested on FreeBSD 9.1-PRERELEASE r243026 (amd64). 

Please provide any additional information below.  
Bug exists in "char *getcmdargs()" function in 
"psutil/arch/bsd/process_info.c", which causes all system memory to be 
allocated, attached patch fixes the issue for me.

Attachment: psutil_bsd_process_leak_fix.patch

Original issue: http://code.google.com/p/psutil/issues/detail?id=339

@giampaolo
Copy link
Owner Author

From g.rodola on November 18, 2012 10:40:38

Fixed in r1547 .
Thanks a lot.

Status: FixedInSVN
Labels: Milestone-0.6.2

@giampaolo
Copy link
Owner Author

From g.rodola on March 02, 2013 04:13:47

Updated csets after the SVN -> Mercurial migration: r1547 == revision 
cea9ff990255 r243026 == revision ???

@giampaolo
Copy link
Owner Author

From g.rodola on April 07, 2013 18:21:49

Status: FixedInHG

@giampaolo
Copy link
Owner Author

From g.rodola on April 11, 2013 02:17:39

Labels: -Milestone-0.6.2 Milestone-0.7.0

@giampaolo
Copy link
Owner Author

From g.rodola on April 12, 2013 11:21:27

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant