#14711: Memleak when creating QuadraticField
-------------------------------------------------+-------------------------
Reporter: jpflori | Owner:
Type: defect | davidloeffler
Priority: critical | Status: new
Component: number fields | Milestone: sage-5.12
Keywords: memleak, number field, | Resolution:
QuadraticField | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: u/SimonKing/ticket/14711 | Commit:
Dependencies: | Stopgaps:
-------------------------------------------------+-------------------------
Comment (by SimonKing):
Replying to [comment:35 SimonKing]:
> Two searches where we currently have only one.
Hmm. This may be not the case, actually. We could continue to only do the
search in `codomain._coerce_from_hash`, which would still be a `MonoDict`,
hence, with weak references to the key (i.e., to the domain). So, the
search would only happen there. But then, depending on the immortality of
the domain resp. the codomain, what we find as value of
`codomain._coerce_from_hash` will be a strong respectively a weak
reference to a map, and then we would have no reference respectively a
strong reference back from the domain to the map.
But still, I fear this will slow down things.
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:36>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
