#4740: [with patch, needs work] Fix memory leak in finite field coercion
----------------------+-----------------------------------------------------
Reporter: mabshoff | Owner: robertwb
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.2.3
Component: memleak | Resolution:
Keywords: |
----------------------+-----------------------------------------------------
Changes (by mabshoff):
* milestone: sage-3.4 => sage-3.2.3
Comment:
Robert,
the leak seems to be gone in 3.2.2:
{{{
----------------------------------------------------------------------
| Sage Version 3.2.2, Release Date: 2008-12-18 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
sage: F = GF(13)
sage: get_memory_usage()
689.02734375
sage: for _ in xrange(10000):
....: t = F.coerce(F(234234))
....:
sage: get_memory_usage()
689.02734375
sage: for _ in xrange(100000):
....: t = F.coerce(F(234234))
....:
sage: get_memory_usage()
689.02734375
sage: for _ in xrange(100000):
....: t = F.coerce(F(234234))
....:
sage: get_memory_usage()
689.02734375
sage:
}}}
Should we close this ticket as won't fix or is the patch her still
relevant? In that case we should update the ticket to reflect the actual
issue being fixed here.
Cheers,
Michael
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4740#comment:4>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
