#4740: Fix memory leak in finite field coercion
----------------------+-----------------------------------------------------
Reporter: mabshoff | Owner: robertwb
Type: defect | Status: new
Priority: major | Milestone: sage-3.2.2
Component: memleak | Keywords:
----------------------+-----------------------------------------------------
Burcin reported at #4639:
{{{
sage: F = GF(13)
sage: get_memory_usage()
708.02734375
sage: for _ in xrange(10000):
....: t = F.coerce(F(234234))
....:
sage: get_memory_usage()
728.15234375
sage: for _ in xrange(100000):
t = F.coerce(F(234234))
....:
sage: get_memory_usage()
932.3125
sage: for _ in xrange(100000):
t = F.coerce(F(234234))
....:
sage: get_memory_usage()
1136.35546875
}}}
Since the patch by RobertWB at that ticket fixes the issue Burcin
reported, but not the original one I am moving it over to this ticket.
Cheers,
Michael
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4740>
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
-~----------~----~----~----~------~----~------~--~---
