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

Process.{get_memory_info, get_ext_memory_info, get_memory_percent} leaks memory. #413

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

Comments

@giampaolo
Copy link
Owner

From thep...@gmail.com on July 26, 2013 01:48:04

What steps will reproduce the problem?  
1. Repeatedly call Process.get_memory_info(), Process.get_ext_memory_info(), 
Process.get_memory_percent()
2. Observe explosive memory usage

for proc in psutil.process_iter():
    proc.get_memory_info() 

What is the expected output?  
Memory usage stays relatively flat 

What do you see instead?  
Consumes tons of memory 

What version of psutil are you using? What Python version?  
psutil 1.0.1
python 2.7.5 

On what operating system? Is it 32bit or 64bit version?  
Windows 7 SP1 32-bit 

Please provide any additional information below.  
Looks like the root issue is the call to 
_psutil_mswindows.get_process_memory_info (and probably 
_psutil_mswindows.get_process_memory_info_2)

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

@giampaolo
Copy link
Owner Author

From g.rodola on July 25, 2013 17:43:34

You're right: I can reproduce the problem with 
_psutil_mswindows.get_process_memory_info_2().
This also means we currently does not have a test case for this.
More later.

@giampaolo
Copy link
Owner Author

From g.rodola on July 26, 2013 08:25:19

Fixed in revision 88c8fd7732c0 .

Status: FixedInHG
Labels: Milestone-1.1.0

@giampaolo
Copy link
Owner Author

From g.rodola on August 09, 2013 02:44:41

Issue 417 has been merged into this issue.

@giampaolo
Copy link
Owner Author

From g.rodola on September 26, 2013 11:46:22

Issue 432 has been merged into this issue.

@giampaolo
Copy link
Owner Author

From g.rodola on September 28, 2013 03:06:18

Status: Fixed

@giampaolo
Copy link
Owner Author

From g.rodola on September 28, 2013 10:32:46

Closing out as fixed. Release 1.1.0 is now available for download.

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