#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:43 nbruin]:
> But that responsibility would fall back onto the homset once the last
reference to a map has been lost. You wouldn't know when that would
happen. Do the maps in the coercion framework really need a Homset?
Perhaps you can just leave that blank if you have `_use_weak_references`.
This could actually be a good idea that would allow to preserve the strong
references of Homsets to domain and codomain. I originally hesitated to
have `Map._parent=None` for maps that are in the coercion framework,
because maps are elements and thus should have parents. But the parent
could easily be reconstructed, provided that domain and codomain of the
coerce map are still alive. And it ''will'' be alive if we access the map,
because accessing it only works if we have the domain and codomain in our
hands.
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:44>
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.
