On Wed, 2002-05-01 at 02:07, James Henstridge wrote: > >I've been experimenting with libglade from Python, and have found that I > >can use up an awful amount of memory incredibly quickly by destroying > >and re-creating widgets. I've written a small script that demonstrates > >it. > > If you could run this under memprof to see which allocations are using > the most memory?
Thanks for the reply. I've downloaded memprof. Can you give me some pointers on what to do with it and what should I look for? (I can execute my script from memprof okay, but I'm not sure what to look out for) > What if you change the labe.destroy() calls to this?: vbox.remove(label) No change, unfortunately. It eats approximately 1MB per second. > If you feel like it, you could also try the latest pygtk 1.99.x release > to see if it has the same problem (much of the code has been rewritten > for the 2.0 release of both pygtk and libglade). I will definitely be having a look at that at some point, but for the moment I have to stick with the old versions as porting the rest of our code base over to 2.0 would be a big job. How solid are the 2.0 python bindings, in comparison to the older versions? -- Graham Ashton _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
