#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 nbruin):
Replying to [comment:222 SimonKing]:
> I am not sure what you mean here by "keys". Are you talking about the
keys of the weak references? Are you talking about the keys of
`WeakValueDictionary`?
Yes. they are the same :-). I was mainly talking about what I tried in
`safeweakdict` and that I think we achieve the same safety that a proper
`SafeWeakValueDict` would provide.
By the way, for me (on Fedora 16) `sage -t -gdb` works like a charm and,
indeed, the backtrace shows this is indeed `gcmodule` leading to
`Delete<polybori::groebner::ReductionStrategy>` leading to an error raise
in `libc`. So either the way polybori is wrapped is wrong or polybori
itself has a "memory drain" (or whatever the reverse of a leak is). Time
for a polybori expert I'd say.
I think it happens via `libs/polybori/decl.pxd`
{{{
void PBRedStrategy_delete "Delete<ReductionStrategy>"(PBRedStrategy
*mem)
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:229>
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.
