#14711: Memleak when creating QuadraticField
-------------------------------------------------+-------------------------
Reporter: jpflori | Owner:
Type: defect | davidloeffler
Priority: critical | Status: new
Component: number fields | Milestone: sage-5.13
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 nbruin):
So one action point: Have you considered just leaving the codomain
strongly referenced? Apart from the fact that `_make_weak` and
`_make_strong` on map compositions still needs to recurse into components,
it should make compositions easier to work with, because the first map
will keep the middle (co)domain alive, as desired.
It also means `_codomain` can remain a fast slot.
I currently don't see a scenario where weakening the codomain reference
buys us anything, especially because maps internally will usually
reference the codomain.
Another action point: see if `_coerce_from_list` can simply be thrown
away.
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:70>
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.
