Re: [Matplotlib-users] Re: memory leaks, 0.54.1 with .2a modifications

[John H. <jdh...@ac...>]

>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:

    Steve> I ran your memory test script on my Fedora 2 PC, it gave
    Steve> Average memory consumed per loop: 168.3600 on the previous
    Steve> matplotlib Average memory consumed per loop: 41.7200 on the
    Steve> latest matplotlib from CVS.  That's a big improvement.

Well that's interesting.  I just reran the script myself because I was
getting approx 12 per loop and you are getting 40.  But now when I
rerun it I get numbers compatible with yours.  Annoying.  Back to the
drawing board.

    Steve> For the last week or so I've been unable to use the GTK+
    Steve> backend with matplotlib (and PyGTK) from CVS. Instead of
    Steve> producing a plot it colors the whole figure black. I think
    Steve> this may be a colormap problem.

From your post to the pygtk list, I assume you are using PyGTK 2.3.93.
Unfortunately I don't have a good platform to test this version on
since my system doesn't have the required glib/gtk version and I have
learned from past experience not to try and upgrade these libs.
0.54.2 with the GTK backend runs fine with pygtk-2.2 on my system.

A couple of questions

 * can you run matplotlib-0.54.1 on your current version of pygtk.
   This will help me figure out if something in matplotlib has changed
   or if something on your system has changed.  The GTK backend is
   fairly stable at this point so not a lot has changed.

 * Can you run matplotlib-0.54.2 with pygtk2.2 on your system?

If there is a 2.3.93 specific problem, we'll need to get it worked
out, but I'd like to narrow the field of candidate problems first.

JDH