[Mono-dev] Re: Mono.Cairo Memory Leak
Manuel, I'm writing an interactive canvas for the MonoUML Case Tool. I'm using Cairo with Gtk# and I have experimented an ascending memory consumption when drawings are continuously performed, for example inside a MotionNotifyEvent Handler. This memory is never released and eventually SWAP memory is needed making all too slow. I attach a simple example that illustrate this problem. Cairo draws a rectangle inside a Gtk.DrawingArea every time that the mouse is moved over the DrawingArea. Compile it, run it, move the mouse, and see how memory consumption starts to getting higher and higher over time. Is anything wrong with my code? or is a bug? You're not calling g.Dispose () or ((IDisposable)g).Dispose (); when you're ready with the object. Rob ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Re: Mono.Cairo Memory Leak
Hi Robert, Thanks for your answer. I have tried to put ((IDisposable)g).Dispose (); just at the end of OnMontionNotifyEvent, but, unfortunately, this does not fix the problem. Manuel. 2005/10/6, Robert Jordan [EMAIL PROTECTED]: You're not calling g.Dispose () or ((IDisposable)g).Dispose (); when you're ready with the object. Rob -- · Manuel Alejandro Cerón Estrada · [EMAIL PROTECTED] · http://ceronman.blogspot.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Re: Mono.Cairo Memory Leak
Hello, On Thu, 2005-10-06 at 13:48 -0500, Manuel Alejandro Cerón Estrada wrote: Hi Robert, Thanks for your answer. I have tried to put ((IDisposable)g).Dispose (); just at the end of OnMontionNotifyEvent, but, unfortunately, this does not fix the problem. Here is the relevant bug: http://bugzilla.ximian.com/show_bug.cgi?id=76230 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
