#4639: bad memory leak with exponentiation
------------------------------+---------------------------------------------
Reporter: bober | Owner: somebody
Type: defect | Status: new
Priority: blocker | Milestone: sage-3.2.1
Component: basic arithmetic | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment (by mabshoff):
Burcin about his code, not the problem reported here:
{{{
[6:36pm] burcin: hmm.. I think I found the problem..
[6:36pm] burcin: still vague though
[6:36pm] mabshoff: burcin: I CCed RobertWB on that existing leak ticket
with the exponentiation and hopefully he will just post a one line patch.
[6:36pm] mabshoff: Ok
[6:36pm] burcin: I was being a good coercion user and called .coerce()
[6:36pm] burcin: if I just use the __call__ on the parent, things work
much much faster
[6:36pm] mabshoff: And it doesn't leak?
[6:37pm] burcin: I am guessing that the leak also goes away.. because this
example ate more than 2gb memory with the leak
[6:37pm] mabshoff: yeah
}}}
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4639#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
