My favorites | Sign in
Project Home Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 3: Possible memory leak
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  xu.mathena
Closed:  Jun 2008


 
Project Member Reported by xu.mathena, Jun 11, 2008
What steps will reproduce the problem?
 Use solve() in pyipopt for a couples of times and memory usage will
significantly increase due to the possible memory leak in callback interface. 

 
Jun 17, 2008
Project Member #1 xu.mathena
Now the memleak bug is gone (at least according to valgrind) 

Also, an extensive test that calling the pyipopt module to solve and close 1000 very
big and different nlp problems only increased the memory usage by less than 1M. Thus,
pyipopt is now more robust. 
Status: Fixed

Powered by Google Project Hosting