#12313: Fix yet another memory leak caused by caching of coercion data
-------------------------------------------------+--------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: memleak | Resolution:
Keywords: coercion weak dictionary | Work issues:
Report Upstream: N/A | Reviewers: Simon King
Authors: Simon King, Jean-Pierre Flori | Merged in:
Dependencies: #715, #11521, #11599 | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by SimonKing):
Replying to [comment:67 jpflori]:
> I already reported such an error in
http://trac.sagemath.org/sage_trac/ticket/12313#comment:24
>
> I did not really pay attention because I could only reproduce it once on
two fresh install of Sage.
>
> It seemed to have been caused by the cparent stuff...
OK. But I wonder: Is it reliably reproducible on the same machine? Namely,
as I said, I have never seen the "2" on my own machine.
What shall we do about that error? After all, it is about how the data are
distributed in the hash table, and the hash is clearly machine dependent
(since the hash depends on the address of the object).
Hence, the output of "stat()" is machine dependent. Perhaps we could mark
the output "random"?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12313#comment:68>
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.
