On Tue, 30 Sep 2008 09:28:51 -0400 "Seth Remington" <[EMAIL PROTECTED]> wrote:
> Hello, > > I am not a member of the list but can confirm the OP's discovery of > the memory leak. I was Googling for this and found this mailing list > post and then noticed that the date was only three days ago (thanks > for the quick indexing Google) and thought I should chime in. > Thanks, I was still waiting to hear if anyone was able to reproduce it. My code does it on two different Linux distros so far. I was hoping I'd someone would just say "it's because you forgot to X", but unfortunately I'm beginning to think it's a bug. > I have a custom cairo widget inheriting from a gtk.DrawingArea that > displays some text and refreshes very frequently. Using cairo's > built-in text rendering (i.e. show_text()) I do not see the memory > leak but when I switched to using pangocairo then I saw the massive > memory growth. > Good to know the Cairo native rendering doesn't leak, I may have to work around it this way. Unfortunately, I don't think the built-in Cairo text rendering supports any sort of markup like Pango does; I am using that heavily in my app. If I'm right, it would be lots of tedious code to position things and set fonts and so forth by hand. :( -Kyle _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
