#12215: Memleak in UniqueRepresentation, @cached_method
-----------------------------+----------------------------------------------
Reporter: vbraun | Owner: rlm
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: memleak | Keywords: UniqueRepresentation
cached_method caching
Work_issues: Fix two tests | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #11115 #11900
-----------------------------+----------------------------------------------
Comment(by SimonKing):
Replying to [comment:63 vbraun]:
> For the record, I have these patches applied on top of sage-4.8.rc0:
> {{{
> 12221_debug.patch
> trac_12247_var_construction.patch
> 9138_flat.patch
> trac11900_category_speedup_combined.patch
> trac11900_only_fix_singleton_hash.patch
> trac11900_doctest.patch
> 11115_flat.patch
> trac_11115_docfix.patch
> trac12215_weak_cached_function.patch
> trac12215_segfault_fixes.patch
> }}}
> removed the `Py_INCREF(self.__domain)` and `Py_INCREF(self.__codomain)`
bandaid. Still no segfault.
Sure. As I stated in some post above, the segfault only results when
applying both #12313 (hence, its dependency #715 as well) ''and'' the
(old) patches from here.
If you only have the (old or new) patches from here or only have
#715+#12313 then there is no segfault.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12215#comment:64>
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.
