#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------+-------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status:
needs_review
Priority: major | Milestone: sage-5.3
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues: Rebase wrt
the new version of #715. Take into account Nils' comments
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 SimonKing):
It is frustrating. The patchbot reports a problem in
sage.rings.padics.padic_base_leaves, that is most likely a cache problem
in coercion: At some point, the absence of coercion is cached even though
there ''is'' a coercion.
I thought that that kind of problem was fixed by #12969! And worse: I do
''not'' get the error reported by the patchbot. And even worse: I ''do''
get the error reported by the patchbot if I additionally apply #13370. And
still worse: For #13370, the patchbot also reports a segfault in another
test - that I can not reproduce.
My plan: Using #13370, I try to find out what side-effect is responsible
for the wrong coercion cache. Hopefully it can then be fixed, in a new
dependency for this ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:132>
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.
