#12616: The LP are not deallocated because of cyclic references !
----------------------------------+-----------------------------------------
   Reporter:  ncohen              |          Owner:  ncohen       
       Type:  defect              |         Status:  needs_review 
   Priority:  major               |      Milestone:  sage-5.0     
  Component:  linear programming  |       Keywords:               
Work_issues:                      |       Upstream:  N/A          
   Reviewer:                      |         Author:  Nathann Cohen
     Merged:                      |   Dependencies:               
----------------------------------+-----------------------------------------
Changes (by ncohen):

  * status:  new => needs_review


Old description:

> Helloooooooooo !!!!
>
> Because of a cyclic reference (the LP pointed toward the LP variables,
> and the LP variables toward the LP), the LP objects were not immediately
> deallocated at the end of functions using them. That produced memory
> problems that have been reported there [1, 2] and there [3].
>
> Thanks to the wonderful people one can find among Sage developpers who
> always have a perfect answer ready for you, here is a patch to fix it.
> It's actually quite straightforward (one of the two references was not
> even necessary, nor even used) when you know where it comes from, but
> without the good hint you can search for a long time `:-D`
>
> Nathann
>
> [1] http://ask.sagemath.org/question/1170/memory-blowup-with-milp
> [2] http://ask.sagemath.org/question/1191/memory-blowup-2
> [3] https://groups.google.com/forum/#!topic/sage-
> devel/4jJbIC5TqVs/discussion

New description:

 Helloooooooooo !!!!

 Because of a cyclic reference (the LP pointed toward the LP variables, and
 the LP variables toward the LP), the LP objects were not immediately
 deallocated at the end of functions using them. That produced memory
 problems that have been reported there :

 http://ask.sagemath.org/question/1170/memory-blowup-with-milp
 http://ask.sagemath.org/question/1191/memory-blowup-2
 http://groups.google.com/forum/#!topic/sage-devel/4jJbIC5TqVs/discussion

 Thanks to the wonderful people one can find among Sage developpers who
 always have a perfect answer ready for you, here is a patch to fix it.
 It's actually quite straightforward (one of the two references was not
 even necessary, nor even used) when you know where it comes from, but
 without the good hint you can search for a long time `:-D`

 Nathann

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12616#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to