#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------------+-------------------
       Reporter:  SimonKing                             |         Owner:        
                                               
           Type:  defect                                |        Status:  
positive_review                                      
       Priority:  major                                 |     Milestone:  
sage-5.7                                             
      Component:  memleak                               |    Resolution:        
                                               
       Keywords:  coercion weak dictionary              |   Work issues:        
                                               
Report Upstream:  N/A                                   |     Reviewers:  Simon 
King, Jean-Pierre Flori, John Perry, Nils Bruin
        Authors:  Simon King, Jean-Pierre Flori         |     Merged in:        
                                               
   Dependencies:  #715, #11521, #12215, #13746, #13378  |      Stopgaps:        
                                               
--------------------------------------------------------+-------------------

Comment (by SimonKing):

 Replying to [comment:297 jpflori]:
 > Maybe we hsould open a "metaticket" to track this regression and point
 there to tickets that will actually fix each of these regressions?

 To my understanding, the memory leak fixes are fine up to and including
 #12215. One could argue that the ticket from here is also fixing a general
 memory leak, and fixing a general leak counts more than a few speed
 regressions in specialised code. But one could argue that we should be
 happy to have the fixes up to #12215 in the next Sage release, and should
 not spoil it with several speed regressions - hence, #12313 should not be
 merged until we found a way to lift the regression.

 I don't know what Jeroen prefers.

 If he intends to merge #12313 soon, then it would make sense to change
 #13911 into a task (=metaticket), the original purpose of #12313 probably
 being solved by #13605.

 If he intends to not merge #12313 before all regressions are solved, then
 I see no benefit in crating a separate metaticket. Instead, one should put
 #12313 as "needs work" and create new tickets for the separate aspects of
 regression, making them dependencies for #12313.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:298>
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].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to