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.

Sign up for GitHub

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

Jump to bottom

Potential memory leak every time we use PyList_New(0) #299

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

Potential memory leak every time we use PyList_New(0) #299

giampaolo opened this issue May 23, 2014 · 4 comments
Assignees
@giampaolo
Labels
enhancement imported memleak

Comments

@giampaolo
Copy link
Owner

From g.rodola on July 04, 2012 10:39:04

Everytime we use PyList_New(0) we're currently forgetting to Py_DECREF the list 
object in case of error.
This affects all the platforms.

Original issue: http://code.google.com/p/psutil/issues/detail?id=299
@giampaolo giampaolo self-assigned this May 23, 2014
@giampaolo
Copy link
Owner Author

From g.rodola on July 04, 2012 06:46:44

Fixed in r1411 , r1412 , r1413 , r1414 .

Status: FixedInSVN

@giampaolo
Copy link
Owner Author

From g.rodola on July 10, 2012 18:31:14

A test suite which is supposed to cover most of the cases explained above has 
been added as r1428 .

@giampaolo
Copy link
Owner Author

From g.rodola on August 13, 2012 09:25:13

Fixed in version 0.6.0, released just now.

Status: Fixed
Labels: -Milestone-1.0.0 Milestone-0.6.0

@giampaolo
Copy link
Owner Author

From g.rodola on March 02, 2013 04:10:25

Updated csets after the SVN -> Mercurial migration: r1411 == revision 
376f3d516316 r1428 == revision d584c17669f0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@giampaolo giampaolo

Labels
enhancement imported memleak
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@giampaolo