#11468: Memleak in multi_polynomial_libsingular.pyx
------------------------+---------------------------------------------------
Reporter: jpflori | Owner: rlm
Type: defect | Status: new
Priority: critical | Milestone: sage-4.7.1
Component: memleak | Keywords: memleak, libsingular
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Changes (by jpflori):
* keywords: memleak, elliptic curves => memleak, libsingular
* type: PLEASE CHANGE => defect
Old description:
> Using the following piece of code makes the memory footprint of sage
> [[BR]] grow indefinitely: [[BR]]
>
> sage: K = GF(1<<50,'t') [[BR]] sage: j = K.random_element() [[BR]] sage:
> while 1: [[BR]] ....: E = !EllipticCurve(j=j) [[BR]] ....: del E
> [[BR]] ....: [[BR]]
>
> This seems to be less dramatic with finite fields of char != 2 and
> [[BR]]inexistant for ZZ and QQ.
>
> However this makes big computations involving different elliptic curves
> quite inpractical.[[BR]]
New description:
Using the following piece of code makes the memory footprint of sage
[[BR]] grow indefinitely: [[BR]]
sage: K = GF(1<<50,'t') [[BR]] sage: R.<x,y> = PolynomialRing(K)
sage: a = K.random_element() [[BR]] sage: while 1: [[BR]] ....: R(a)[[BR]]
....:
So there is some memleak while creating elements of multivariate
polynomial ring implemented with libsingular.
See http://groups.google.com/group/sage-
support/browse_thread/thread/9a8e887df34a8e9a for further discussion.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11468#comment:1>
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.
