Hi; On Mon, 2008-03-31 at 18:14 +0300, Tommi Komulainen wrote: > On Sun, Mar 30, 2008 at 2:51 AM, Matthew Allum <[EMAIL PROTECTED]> wrote: > > > > The X11 backend is not cleaning up properly as yet when an extra stage > > is closed but its not crashing (but is emitting warnings). It shouldn't > > be anything that major, I'll take a look asap if you dont beat me to it. > > OK, attached patches should fix the immediate issues I've found.
Okeys dokes. I will commit at least first one (see below on others). > > Destroying the stage raises an interesting issue regarding memory > management, I think. How should the lifecycle of behaviours and > timelines be managed in such a case? > > The very least behaviours should notice when actors get destroyed and > stop updating them, but it could be convenient to be able to 'attach' > a timeline/behaviour to actor(s) so that when all actors are gone, so > would the timeline. Quite similar to floating references and > containers, but in reverse. > > Thoughts? Really need some input from Ebassi on this stuff. It seems the cleanup is going to be a little tougher than expected. I've at least now got rid of the warnings on glx stage destruction, I suspect there is some leakage / missing cleanup here stil however. Also beginning to look at making the stage creation work a little more regular as well as ability to subclass. Another quite serious issues I've discovered is the trunk gtk clutter widget now takes out an X server :/ (both Intel and ATI). No clue as yet as to why this is now happening. Many thanks; == Matthew -- To unsubscribe send a mail to [EMAIL PROTECTED]
