#14356: memleak in UniqueRepresentation / Poset
---------------------------+------------------------------------------------
Reporter: vbraun | Owner: rlm
Type: defect | Status: needs_info
Priority: major | Milestone: sage-5.9
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------+------------------------------------------------
Changes (by vbraun):
* cc: SimonKing, tscrim (added)
* status: new => needs_info
Comment:
It seems that this is a rather common use of posets: You have some objects
that refer back to their common container. Now label the poset elements
with. This then keeps everything alive.
Questions:
* Poset has an optional `key=` argument, but it is seems to be not used by
!UniqueRepresentation. Whats up with that?
* Maybe Poset should support for weakly referenced labels?
* !UniqueRepresentations could check that the key does not have a
reference to the value for debugging purposes
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14356#comment:1>
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.
