#12313: Fix yet another memory leak caused by caching of coercion data
-------------------------------------------------+--------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status:
positive_review
Priority: major | Milestone: sage-5.1
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers: Simon King,
Jean-Pierre Flori, John Perry
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #715, #11521, #11599 | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by SimonKing):
Hi Jean-Pierre,
Replying to [comment:105 jpflori]:
> So far I could reproduce the problem in ell_tate_curve above (after
about 10 runs, so quite often) on:
> * 5.0.beta13 + #715 + #11521 + #12313
> ...
> I'm currently testing 5.1.beta0 + #12313 (after about 40 tries, no
errors, which is quite disturbing).
Aha. So, seemingly it is the combination of the weak coercion caches from
#715 and #11521, plus the weak unique parent caches from here. Is there
any hint what objects are involved in the crashes?
My gut feeling is that actions are involved: By #715, they only store a
weak reference to the underlying set (which I felt was dangerous, but was
needed to fix some memory leak, and seemed justifiable after all). I could
imagine that the underlying set of some action becomes garbage collectable
with #12313.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:106>
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.
