#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:
-------------------------------+------------------------
Changes (by nbruin):
* cc: SimonKing (added)
Comment:
Sadly, this is most definitely a memory leak and, as shown above, not one
in python space. The most likely suspect is !LibSingular, especially
because we already know that we're not interfacing with !LibSingular
reference counting properly. This might be a particularly easy example to
trace through, so it may be worth doing, because it might show the way to
proper LibSingular memory management. Just to confirm:
{{{
sage: R = PolynomialRing(QQ, 'x', 2)
sage: count = 0
sage: p = get_memory_usage()
sage: while R.ideal(1) == R.ideal(1):
....: count += 1
....: if (count%1000 == 0):
....: print get_memory_usage(p)
....: p = get_memory_usage()
....:
27.21875
26.61328125
26.76953125
26.62890625
26.62109375
......
}}}
i.e., each batch of 1000 iterations grows memory use very consistently.
--
Ticket URL: <http://trac.sagemath.org/ticket/15498#comment:2>
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.
