#14059: Fix refcount/deallocation of integers
------------------------------+---------------------------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-5.7
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Jean-Pierre Flori
Authors: Simon King | Merged in:
Dependencies: | Stopgaps:
------------------------------+---------------------------------------------
Comment (by nbruin):
Replying to [comment:58 jpflori]:
> Don't know. Maybe speed?
Indeed. Types that are not container type (types that do not hold
references to other python objects) need not be tracked by GC. I don't
think Cython supports "not GC tracked" by default. Basically all Sage
objects formally are container types because they have a _parent pointer
or something like that.
Integers do too, but since ZZ is supposed to be immortal anyway, it
doesn't matter.
It means that
{{{
del ZZ
}}}
would not lead to ZZ actually being deallocated (even if there are no
other references to it anymore, because `ZZ.one_element` would have a
pointer to `ZZ` that can't be discovered to be part of the cycle by GC.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14059#comment:59>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
