#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 jpflori):
Replying to [comment:106 SimonKing]:
> 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.
The problem occurs while multiplying an element of a ring and its field of
fractions.
I did not think it through at all, but my natural guess would be that this
is done by (canonical?) coercion of the ring element into the field of
fractions and then the action takes place there.
That would correspond to the "canonical_coercion" and
PyObject_CallObject(...) calls within the bin_op call made by the coercion
model, hence no actions involved, but I'm still confused by all of this ;)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:111>
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.
