Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=81153 --- shadow/81153 2007-03-20 10:01:58.000000000 -0500 +++ shadow/81153.tmp.12079 2007-03-20 14:43:18.000000000 -0500 @@ -120,6 +120,18 @@ This also explains why moving the Dispose of the Graphics instances earlier "hides" the problem (the X handle is still valid at that time, but not later). Note: running this sample under valgrind didn't report anything useful (well it's useful to know it's not a memory corruption). + +------- Additional Comments From [EMAIL PROTECTED] 2007-03-20 14:43 ------- +yeah, rolf just mentioned this in IRC. + +maybe we need way to have Graphics.cs notify us that a graphics object +is being created for use with an Hwnd? maybe a private static +property that WMF will set and Graphics.cs will make a method call on +when it creates a new Graphics object? + +I don't think there's any way around this ordering - we have to +guarantee the destruction of the cairo Pictures before the X drawable +they refer to. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
