#17360: memory leak in FiniteDimensionalAlgebra
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.5
Component: memleak | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/algebra_memoryleak | 2c942ad50c3f9947b7d680d2f6cc708848ac9758
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by tscrim):
I'm thinking we should change this ticket to take care of the
`CategoryWithAxiom` leak.
I can get rid of the memory leak by removing the caching on
`Category._with_axiom_as_tuple` and `Category._with_axiom` (although it
takes a few passes of `gc.collect()` to get rid of the finite fields).
However I believe this could lead to a slowdown in instantiating
categories, and we have the workaround of the memory leak of
`Algebras(Fields())`.
So perhaps what we can do is have the cached part should be at the class
level (which should cover the heavy lifting and result in a large speedup
in [Nils] creation because the construction won't be done for every new
`Algebras` category) and the caching should return a class. Thoughts?
--
Ticket URL: <http://trac.sagemath.org/ticket/17360#comment:12>
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/d/optout.
