#715: Parents probably not reclaimed due to too much caching
----------------------------+-----------------------------------------------
Reporter: robertwb | Owner: somebody
Type: defect | Status: needs_work
Priority: major | Milestone: sage-4.8
Component: coercion | Keywords: weak cache coercion
Work_issues: fix doctests | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #9138, #11900
----------------------------+-----------------------------------------------
Comment(by SimonKing):
Meanwhile I am rather desperate: I have not the faintest idea how the
segfault occurs.
Therefore I used some debugging function that I registered using
`sys.settrace(...)`, so that all Python commands in the critical example
are written into a file.
I posted logs for the
[http://sage.math.washington.edu/home/SimonKing/SAGE/tickets/715/fulltrace
unpatched] and the
[http://sage.math.washington.edu/home/SimonKing/SAGE/tickets/715/fulltracePatched
patched] version.
There is one obvious difference of the two logs: The hash is called more
often in the patched version. Calling the hash is rather inefficient for
matrix spaces: Each time when the hash of a matrix space is called, the
matrix space's string representation is created, which is slow. I suggest
to cache the hash value (like what I did for polynomial rings in #9944),
but this should be on a different ticket.
Apart from that, I can't spot an obvious difference. Do you have any clue?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/715#comment:47>
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.
