#12905: Memory leaks with Cliquer
---------------------------------+------------------------------------------
       Reporter:  ncohen         |         Owner:  jason, ncohen, rlm
           Type:  defect         |        Status:  needs_review      
       Priority:  major          |     Milestone:  sage-5.4          
      Component:  graph theory   |    Resolution:                    
       Keywords:                 |   Work issues:                    
Report Upstream:  N/A            |     Reviewers:  David Coudert     
        Authors:  Nathann Cohen  |     Merged in:                    
   Dependencies:                 |      Stopgaps:                    
---------------------------------+------------------------------------------
Changes (by ncohen):

  * status:  needs_work => needs_review


Old description:

> Geoff reported on http://ask.sagemath.org/question/1170/memory-blowup-
> with-milp memory leaks in Sage. Turns out there were two to solve, and
> one of them was fixed in #12903.
> The other one comes from Cliquer and is solved with this patch. Here's
> what it does :
>
>  * Solves memory leaks reported by Geoff
>  * Incidentally updates Cliquer to version 1.21
>  * Incidentally removes Sage's code that was formerly directly inserted
> in the original Cliquer files. This code is now inserted during the SPKG
> installation from patches located in the SPKG's patches/ folder.
>
> As a result, no one should be scared anymore of running the following
> lines :
>
> {{{
> for i in range(2000):
>     print get_memory_usage()
>     _ = graphs.RandomGNP(30,.2).cliques_maximum()
> }}}
>
> {{{
> for i in range(2000):
>     print get_memory_usage()
>     _ = graphs.RandomGNP(30,.2).clique_number()
> }}}
>
> {{{
> for i in range(2000):
>     print get_memory_usage()
>     _ = graphs.RandomGNP(30,.2).clique_maximum()
> }}}
> Apply:
>     * [attachment:trac_12905.patch]
>
> Install the new version of Cliquer:
>     * http://www.steinertriples.fr/ncohen/cliquer-1.21.p11.spkg

New description:

 Geoff reported on http://ask.sagemath.org/question/1170/memory-blowup-
 with-milp memory leaks in Sage. Turns out there were two to solve, and one
 of them was fixed in #12903.
 The other one comes from Cliquer and is solved with this patch. Here's
 what it does :

  * Solves memory leaks reported by Geoff
  * Incidentally updates Cliquer to version 1.21
  * Incidentally removes Sage's code that was formerly directly inserted in
 the original Cliquer files. This code is now inserted during the SPKG
 installation from patches located in the SPKG's patches/ folder.

 As a result, no one should be scared anymore of running the following
 lines :

 {{{
 for i in range(2000):
     print get_memory_usage()
     _ = graphs.RandomGNP(30,.2).cliques_maximum()
 }}}

 {{{
 for i in range(2000):
     print get_memory_usage()
     _ = graphs.RandomGNP(30,.2).clique_number()
 }}}

 {{{
 for i in range(2000):
     print get_memory_usage()
     _ = graphs.RandomGNP(30,.2).clique_maximum()
 }}}
 Apply:
     * [attachment:trac_12905.patch]

 Install the new version of Cliquer:
     * http://www.steinertriples.fr/ncohen/cliquer-1.21.p0.spkg

--

Comment:

 New spkg :
 http://www.steinertriples.fr/ncohen/cliquer-1.21.p0.spkg

 Should be fine now `:-)`

 God, I had almost forgotten this trac ticket `^^;`

 Nathann

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12905#comment:7>
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