#13731: Fix libsingular memory management
--------------------------------------------------------------+-------------
       Reporter:  nbruin                                      |         Owner:  
rlm     
           Type:  defect                                      |        Status:  
new     
       Priority:  major                                       |     Milestone:  
sage-5.6
      Component:  memleak                                     |    Resolution:  
        
       Keywords:                                              |   Work issues:  
        
Report Upstream:  Fixed upstream, in a later stable release.  |     Reviewers:  
        
        Authors:  Nils Bruin, Simon King                      |     Merged in:  
        
   Dependencies:                                              |      Stopgaps:  
        
--------------------------------------------------------------+-------------

Comment (by SimonKing):

 `make test` reports
 {{{
         sage -t  -force_lib "devel/sage/sage/graphs/graph_generators.py" #
 Killed/crashed
         sage -t  -force_lib "devel/sage/sage/misc/sageinspect.py"
 Total time for all tests: 6884.7 seconds
 make: *** [test] Fehler 132
 simon@linux-sqwp:~/SAGE/debug/sage-5.5.rc0> echo $SINGULAR_XALLOC
 yes
 simon@linux-sqwp:~/SAGE/debug/sage-5.5.rc0> echo $MALLOC_CHECK_
 3
 }}}

 To be on the safe side, can you verify that I did not misspell the
 environment variable? I.e., is there a trailing underscore?

 Note that the error in sageinspect is due to the fact that I also had
 #11768 applied, which needs work. I don't know if the crash in
 graph_generators is related.

 Is that good or bad?

 * It is good, since the xalloc version of Singular works very well, and
 the crashes we discussed here have apparently been fixed upstream (and the
 fixes backported). Hence, I am now going to finalise the spkg for review.
 * It is bad, since I think we had hoped that we see easy-to-analyse
 crashes in garbage collection - after all, I am using sage-5.5.rc0, which
 has some of the weak reference patches applied. But if there is no crash,
 there is nothing to analyse.

 However, if I recall correctly, the crashes did only occur when also
 considering #12215, not only #715 and #11521.

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