#15498: Memory leak in ideal arithmetic
-------------------------------+------------------------
Reporter: ppurka | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.4
Component: algebra | Resolution:
Keywords: memory leak | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Comment (by SimonKing):
I tried this in Singular:
{{{
> ring R = 0, (x,y), dp;
> ideal I = 1;
> for (int count=0; 1; count++)
. { print((memory(1),memory(2)), "%;");
. I = ideal(groebner(I)[1]);
. }
}}}
The memory consumption is constant, but I suppose that's because Singular
knows that if an ideal is generated by a single element then this element
is a standard basis:
{{{
> ideal I = x;
// ** redefining I **
> attrib(I, "isSB");
1
}}}
So, let's try with a different case:
{{{
> ideal I = x,y;
> for (int count=0; 1; count++)
. { if (count%1000==0) {print((memory(1),memory(2)), "%;");}
. I = ideal(groebner(I)[1]) + ideal(groebner(I)[2]));
. if (attrib(I, "isSB")) {print("not good");} //just to be sure it
isn't known to be standard
. }
2232320 2268160
2232320 2268160
2232320 2268160
2232320 2268160
2232320 2268160
2232320 2268160
2232320 2268160
2232320 2268160
}}}
So, it seems that the leak is in Sage and not in Singular, which I think
is not a surprise.
--
Ticket URL: <http://trac.sagemath.org/ticket/15498#comment:15>
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/d/optout.
