#11521: Use weak references to cache homsets
--------------------------------------------------+-------------------------
       Reporter:  jpflori                         |         Owner:  robertwb    
                 
           Type:  defect                          |        Status:  
positive_review              
       Priority:  major                           |     Milestone:  sage-5.5    
                 
      Component:  coercion                        |    Resolution:              
                 
       Keywords:  sd35                            |   Work issues:              
                 
Report Upstream:  N/A                             |     Reviewers:  Jean-Pierre 
Flori, Nils Bruin
        Authors:  Simon King                      |     Merged in:              
                 
   Dependencies:  #12969; to be merged with #715  |      Stopgaps:              
                 
--------------------------------------------------+-------------------------

Comment (by SimonKing):

 Replying to [comment:174 jpflori]:
 > > I have always tested these tickets together.
 > This is not completely clear, do you mean:
 > * #715 without the strong cache + #11521 (which is highly unprobable
 because of the bsd segfault, but let's mention this solution)?

 This isn't a solution, because of the segfault.

 > * #715 with strong cache + #11521?

 Yes. Do the tests pass in that setting?

 > * #715 + #11521 + #13447 (assuming the strong cache is removed either
 from #715 directly or by means of a second reverse patch in #13447)?

 That would be the long term aim, from my perspective. But getting the
 refcount right turned out to be trickier than I originally thought. Hence,
 for now (again: ''IF'' the tests pass) I'd prefer #715+#11521 with the
 ugly strong cache for polynomial rings.

 > > Plus, we ''know'' why a strong cache prevents the problems observed.
 > I guess you mean the bsd bug.
 > Not the memory leaks problems these tickets try to tackle, is that
 right?

 Yes and no. A strong cache for polynomial rings would mean that my current
 Sage applications would eat too much memory - hence, yes, a strong cache
 is opposite to the spirit of these tickets. However, for all other
 parents, these the tickets would still fix some memory leaks.

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