#6623: Memory leak when calling binomial
-----------------------+----------------------------------------------------
Reporter: hartke | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-4.1.3
Component: symbolics | Keywords: binomial, leak
Reviewer: | Author:
Merged: |
-----------------------+----------------------------------------------------
Changes (by kcrisman):
* milestone: => sage-4.1.3
Comment:
Perhaps Pari, or our wrapping of it, is the problem. Do the same thing as
above, but replace
{{{
r=binomial(x,y)
}}}
with
{{{
r=pari(x).binomial(y)
}}}
and you get the same thing. Interestingly, the memory change is *exactly*
3 MB. I can also get similar results using pari(x).gcd(y), except exactly
twice the memory is lost. Also, changing the size of the xrange makes
less memory get lost, and then seems to break the spell a bit.
At any rate, it doesn't seem to happen for small ranges, does for bigger
ones, with more memory lost. If input is not random, definitely hard to
reproduce. Totally naively, could there be too many new_gen's for Pari to
handle after a certain point?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6623#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 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
-~----------~----~----~----~------~----~------~--~---
