#621: memory still reachable in matrix_integer_dense_Matrix_integer_dense
----------------------------+-----------------------------------------------
Reporter: mabshoff | Owner: mabshoff
Type: defect | Status: closed
Priority: major | Milestone: sage-duplicate/invalid/wontfix
Component: memleak | Resolution: duplicate
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: Karl-Dieter Crisman
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------+-----------------------------------------------
Changes (by jdemeyer):
* status: positive_review => closed
* reviewer: => Karl-Dieter Crisman
* resolution: => duplicate
Old description:
> This is caused when running Sage 2.8.3.6+malb's fix for #566:
> {{{
> for i in range(3):
> get_memory_usage()
> m = ModularSymbols(501,2).decomposition(3);
> del m; ModularSymbols_clear_cache();
> get_memory_usage()
> }}}
> and results in
> {{{
> ==8920== LEAK SUMMARY:
> ==8920== definitely lost: 1,518,830 bytes in 183,739 blocks.
> ==8920== indirectly lost: 288,408 bytes in 610 blocks.
> ==8920== possibly lost: 489,439 bytes in 1,002 blocks.
> ==8920== still reachable: 160,311,066 bytes in 872,845 blocks.
> ==8920== suppressed: 0 bytes in 0 blocks.
> }}}
> The exact problem:
> {{{
> ==8920== 2,603,712 bytes in 5 blocks are still reachable in loss record
> 2,370 of 2,372
> ==8920== at 0x4A05A66: malloc (vg_replace_malloc.c:207)
> ==8920== by 0x205E1766:
> __pyx_f_20matrix_integer_dense_20Matrix_integer_dense___new__
> (matrix_integer_dense.c:2966)
> ==8920== by 0x205E1BE0:
> __pyx_tp_new_20matrix_integer_dense_Matrix_integer_dense
> (matrix_integer_dense.c:17692)
> ==8920== by 0x45A272: type_call (typeobject.c:422)
> ==8920== by 0x4156A2: PyObject_Call (abstract.c:1860)
> ==8920== by 0x480783: PyEval_EvalFrameEx (ceval.c:3775)
> ==8920== by 0x4865EF: PyEval_EvalCodeEx (ceval.c:2831)
> ==8920== by 0x4845B3: PyEval_EvalFrameEx (ceval.c:3660)
> ==8920== by 0x4865EF: PyEval_EvalCodeEx (ceval.c:2831)
> ==8920== by 0x4CFF37: function_call (funcobject.c:517)
> ==8920== by 0x4156A2: PyObject_Call (abstract.c:1860)
> ==8920== by 0x41BE0C: instancemethod_call (classobject.c:2497)
> }}}
>
> Cheers,
>
> Michael
New description:
This is caused when running Sage 2.8.3.6+malb's fix for #566:
{{{
for i in range(3):
get_memory_usage()
m = ModularSymbols(501,2).decomposition(3);
del m; ModularSymbols_clear_cache();
get_memory_usage()
}}}
and results in
{{{
==8920== LEAK SUMMARY:
==8920== definitely lost: 1,518,830 bytes in 183,739 blocks.
==8920== indirectly lost: 288,408 bytes in 610 blocks.
==8920== possibly lost: 489,439 bytes in 1,002 blocks.
==8920== still reachable: 160,311,066 bytes in 872,845 blocks.
==8920== suppressed: 0 bytes in 0 blocks.
}}}
The exact problem:
{{{
==8920== 2,603,712 bytes in 5 blocks are still reachable in loss record
2,370 of 2,372
==8920== at 0x4A05A66: malloc (vg_replace_malloc.c:207)
==8920== by 0x205E1766:
__pyx_f_20matrix_integer_dense_20Matrix_integer_dense___new__
(matrix_integer_dense.c:2966)
==8920== by 0x205E1BE0:
__pyx_tp_new_20matrix_integer_dense_Matrix_integer_dense
(matrix_integer_dense.c:17692)
==8920== by 0x45A272: type_call (typeobject.c:422)
==8920== by 0x4156A2: PyObject_Call (abstract.c:1860)
==8920== by 0x480783: PyEval_EvalFrameEx (ceval.c:3775)
==8920== by 0x4865EF: PyEval_EvalCodeEx (ceval.c:2831)
==8920== by 0x4845B3: PyEval_EvalFrameEx (ceval.c:3660)
==8920== by 0x4865EF: PyEval_EvalCodeEx (ceval.c:2831)
==8920== by 0x4CFF37: function_call (funcobject.c:517)
==8920== by 0x4156A2: PyObject_Call (abstract.c:1860)
==8920== by 0x41BE0C: instancemethod_call (classobject.c:2497)
}}}
Duplicate of #620.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/621#comment:10>
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.
