#15498: Memory leak in ideal arithmetic
-------------------------------+------------------------
Reporter: ppurka | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.1
Component: algebra | Resolution:
Keywords: memory leak | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Comment (by SimonKing):
I can confirm that this time it is not a problem with cyclic garbage
collection, as the number of objects tracked by the gc module does not
increase:
{{{
sage: R = PolynomialRing(QQ, 'x', 2)
sage: count = 0
sage: p = get_memory_usage()
sage: import gc
sage: _ = gc.collect()
sage: l = len(gc.get_objects())
sage: while R.ideal(1) == R.ideal(1):
....: count += 1
....: if (count%1000 == 0):
....: _ = gc.collect()
....: print get_memory_usage(p), len(gc.get_objects())-l
....: p = get_memory_usage()
....:
26.8984375 183
26.15234375 183
26.01171875 183
25.890625 183
26.15234375 183
26.0078125 183
25.890625 183
26.15234375 183
26.0078125 183
25.890625 183
26.15234375 183
26.0078125 183
26.015625 183
...
}}}
So, it could actually be that the Sage code triggers a memory leak in
Singular.
--
Ticket URL: <http://trac.sagemath.org/ticket/15498#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
