#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:65 vbraun]:
> I ran all doctests and there are a few crashes in `functor.so`
elsewhere. I didn't have to apply any additional patches.
What exactly do you mean? Do you have the ''old'' patches from here
applied (i.e., without the new `__dealloc__` method), or does the segfault
even occur with the ''new'' patches?
Is it normal that both you and me see segfaults, and it seems to be
analogous problems (namely double deallocation), but we see it in
different examples and with different patches (namely, even with the
''old'' patches from here, all tests pass for me)?
> It dies with
> ...
> It seems that its just memory corruption that manifests itself by
freeing the object twice.
So, you can confirm that it is the same object.
> But the error is presumably elsewhere. Also the gdb stack trace is
completely corrupted.
That sounds like one should write a complete log of all python code
executed - according to your suggestion that the error somewhere occurs
during a Python method.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12215#comment:67>
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.
