imshow memory leak in pylab mode?

Dear all,

I'm not sure if this is by design or a problem:

In a pylab session, if I repeatedly call imshow with the same image, memory increases each time.
This does not happen if i go the 'Artists' way (fig = .., ax = fig.add---, im = ax.imshow)
Is there a way to avoid memory consumption like this in the pylab style?
Even a clf() does not release the memory.
My config is the latest Enthought distribution in 32-bit mode for MacOS.

BR,
Michael

Can you post a complete free-standing script that we can run which
exposes the problem? Also please report your version numbers -- we
could look them up from enthought perhaps but you can help us :slight_smile:

http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html#troubleshooting

ยทยทยท

On Mon, Jul 12, 2010 at 4:06 PM, K.-Michael Aye <kmichael.aye@...287...> wrote:

Dear all,

I'm not sure if this is by design or a problem:

In a pylab session, if I repeatedly call imshow with the same image,
memory increases each time.
This does not happen if i go the 'Artists' way (fig = .., ax =
fig.add---, im = ax.imshow)
Is there a way to avoid memory consumption like this in the pylab style?
Even a clf() does not release the memory.
My config is the latest Enthought distribution in 32-bit mode for MacOS.