#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------+-------------------------
Reporter: SimonKing | Owner:
Type: defect | Status:
needs_review
Priority: major | Milestone: sage-5.3
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: #11521, #11599, #12969, #12215 | Stopgaps:
--------------------------------------------------+-------------------------
Comment (by jpflori):
Replying to [comment:153 SimonKing]:
> Replying to [comment:150 jpflori]:
> > Wouldn't it be easier to directly look at the Cython code for the
<object> refcount?
>
> No idea how to do so.
For the Sage library, you can find the C[++] generated files in
devel/sage...
For files generated on the file, you have to look in .sage/temp/... or
something like this, involving the PID of the process.
Anyway, I had a look at the parent.c file produced from parent.p?? on a
vanilla from coercion 5.3.beta2 and on the lines corresponding to a
{{{return <object> PY_TYPE(x)}}}
there indeed seems to be a _ _Pyx_INCREF called on the address of the
returned value.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:155>
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.
