#13741: Proper deallocation of the (unique) pari instance
-------------------------------------+--------------------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.5
Component: memleak | Resolution:
Keywords: pari deallocation | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by jpflori):
I don't think allocating a second instance is possible at all because of C
stuff in PARI which would get overwritten (e.g. calling pari_init twice in
a row would not be that nice).
We could hope to be able to properly shutdown the PARI instance and
reinstantiating it, but that looks non-trivial.
E.g. some gen elements are defined in gen.pyx at the top level and point
to the unique PARI.
So we should first list all of them, delete them properly, then
reinstantiate PARI.
Fortunately for us, in a normal use, this is done automatically by Python
upon exit (and thanks to your patch the unique PARI instance lives long
enough).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13741#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
