#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 jpflori):
Replying to [comment:28 nbruin]:
> Yes, we have run into these things repeatedly. We're storing maps as
`_coerce_from` and `_convert_from` on the codomain because for those maps,
the codomain needs the domain to exist anyway (a polynomial ring will be
holding a reference to its coefficient ring, a quotient ring needs the
ring it was quotiented from).
>
> This goes very wrong when we have maps into LARGER rings that exist
independently. Indeed, as soon as you're coercing/converting/embedding a
number field into Qbar, into SR, or into CC, your ring has been damned
with virtually eternal life (SR is one ring to forever in the darkness
bind them...).
I think weak caching the domain should solve this problem (unless some
homset as Simon mentioned comes into play).
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:30>
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.
