Hi matplotlib users,
I'm using matplotlib for a long running process. Unfortunately the memory
usage continue to grow as the process runs. I have appended a simple example
which illustrates this at the end of this mail. Unfortunately I haven't
figured out how to use the information obtainable
Jesper Larsen wrote:
Hi matplotlib users,
I'm using matplotlib for a long running process. Unfortunately the memory
usage continue to grow as the process runs. I have appended a simple example
which illustrates this at the end of this mail. Unfortunately I haven't
figured out how to use
Jeff Whitaker wrote:
Jesper Larsen wrote:
Hi matplotlib users,
I'm using matplotlib for a long running process. Unfortunately the memory
usage continue to grow as the process runs. I have appended a simple example
which illustrates this at the end of this mail. Unfortunately I haven't
Eric Firing wrote:
Jeff Whitaker wrote:
Jesper Larsen wrote:
Hi matplotlib users,
I'm using matplotlib for a long running process. Unfortunately the
memory usage continue to grow as the process runs. I have appended a
simple example which illustrates this at the end of this mail.
On 3/26/07, Jeff Whitaker [EMAIL PROTECTED] wrote:
Jesper: For now I recommend adding 'pylab.cla()' after the fig.clear()
as a workaround. I don't really understand why that is necessary -
perhaps John or Eric can clarify whether this is indeed a bug.
I suggest adding a gc.collect after
On 3/26/07, Jeff Whitaker [EMAIL PROTECTED] wrote:
John Hunter wrote:
John: Nope, that has no effect. What does cla clean up that clf doesn't?
Well, it flushes all the lines, removes the ticks, that kind of thing.
But fig.clear sets
self.axes = []
so if there are no references to the axes
