#12357: Make groupoids garbage collectable
---------------------------------------------+------------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_work
Priority: major | Milestone: sage-pending
Component: memleak | Resolution:
Keywords: groupoid cache Cernay2012 | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: #715, #12313, #11943 | Stopgaps:
---------------------------------------------+------------------------------
Comment (by SimonKing):
I had a test that works like "Create an object and store its memory
address; delete it, do garbage collection, create the object again and
show that the memory address is different from the old".
Of course, that is very fragile. By chance, when applying a totally
unrelated ticket, the test breaks for me.
Therefore I made a change in the first patch. The test now verifies that
the stored memory address does not occur among the memory addresses of
uncollectable objects, after garbage collection.
I did not change the dependencies, yet. But perhaps the reviewer has an
opinion on that matter?
Apply trac12357_internal_strong_groupoid_cache.patch
trac12357_reviewer.patch
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12357#comment:13>
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.
