#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 SimonKing):
For the record: When I do not weaken the maps on `_coerce_from_list` or
`_convert_from_list`, the crash vanishes, but the memory leak is still
fixed.
Also in my unpublished branch: Skip invalid maps in discover coercion (in
the backtracking algorithm). But this is just an additional safety. I
think we want that explicitly registered maps (i.e., those which are the
fundamental path ways in the backtracking algorithm) will stay alive.
Hence, it might even be worth while to keep an explicit reference to the
domain of the map, so that the map will remain valid even if something
weakens it.
I am now running tests again.
--
Ticket URL: <http://trac.sagemath.org/ticket/14711#comment:81>
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.
