#8905: Memory leak in echelon over QQ
-------------------------+--------------------------------------------------
Reporter: SimonKing | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone: sage-4.4.2
Component: memleak | Keywords: memleak echelonize
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------+--------------------------------------------------
Comment(by SimonKing):
Similarly, one gets
{{{
sage: MS = MatrixSpace(QQ,8)
sage: M = MS.random_element()
sage: M = M.stack(M)
sage: v = copy(M).left_kernel()
sage: n = 0
sage: mem = get_memory_usage()
sage: while(1):
....: n+=1
....: if get_memory_usage()>mem:
....: mem = get_memory_usage()
....: print mem,n
....: v = copy(M).left_kernel()
....:
800.3828125 27
800.51171875 62
800.640625 94
800.76953125 151
801.05078125 168
801.1796875 187
801.30859375 221
801.4375 256
801.56640625 278
801.71484375 314
802.08984375 375
802.21875 423
802.34765625 460
802.4765625 497
802.60546875 521
802.8984375 610
803.02734375 635
803.15625 690
}}}
I guess the two are related.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8905#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.
