#12313: Fix yet another memory leak caused by caching of coercion data
--------------------------------------------------+-------------------------
Reporter: SimonKing | Owner:
Type: defect | Status:
needs_review
Priority: major | Milestone: sage-5.3
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers: Simon King,
Jean-Pierre Flori, John Perry
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #11521, #11599, #12969, #12215 | Stopgaps:
--------------------------------------------------+-------------------------
Comment (by jpflori):
Replying to [comment:227 SimonKing]:
> gdb just totally hangs. 0% CPU according to htop.
I got a similar problem in #12173.
FLINT wants to free the memory it uses upon quitting, but Sage/Python
tries to do the same upon deletion of Sage objects.
The solution we adopted was to let the FLINT memory (not all of it
fortunately) in place, although that would to memory leaks if one would
load and quit Sage several times from one Python interpreter.
We never figured out how in which order things were deallocated when
Python was shutdown.
And GDB just hanged the same on the double free errors.
On your example, quite strangely, I get a nice segfault and backtrace as
Nils.
Anyway, it could be possible that the situation is as in FLINT: some Sage
method tries to directly deallocate something after we called the Polybori
cleanup method which already freed taht piece of memory and it crashes.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:230>
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.
