Oh, I don't think it's necessarily a leak. Simply a ton
> of unreachable stuff lying around, which a call to
> gc.collect() may help with.
I hope you're right -- matplotlib uses a lot of cyclic references.
But if he's using the pylab interface to manage the figure windows,
the destroy event of the window manager already triggers a call to
gc.collect in the _pylab_helpers module.
JDH
John Hunter wrote:
"Fernando" == Fernando Perez <Fernando.Perez@...179...> writes:
> Oh, I don't think it's necessarily a leak. Simply a ton
> of unreachable stuff lying around, which a call to
> gc.collect() may help with.I hope you're right -- matplotlib uses a lot of cyclic references.
But if he's using the pylab interface to manage the figure windows,
the destroy event of the window manager already triggers a call to
gc.collect in the _pylab_helpers module.
Never mind then. If gc.collect is already called reasonably often, an extra manual call will do zilch. Sorry.
Best,
f