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 rolfkvinge at ya.com.http://bugzilla.ximian.com/show_bug.cgi?id=81093
--- shadow/81093 2007-03-19 09:02:07.000000000 -0500
+++ shadow/81093.tmp.4536 2007-03-19 12:32:26.000000000 -0500
@@ -322,6 +322,14 @@
To avoid (some of) that I started using "using" or explicit Dispose in
newer tests so any crash occurs in the "right" test (but that doesn't
help for existing tests). Also adding a CG.Collect in the [TearDown]
or [TestFixtureTearDown] may also help (didn't try that one).
Good luck!
+
+------- Additional Comments From rolfkvinge at ya.com 2007-03-19 12:32 -------
+One idea would be to add an ID to every Graphics, print it on
+Graphics creation and on dispose, then run the test and you'll have
+the ID of the Graphics causing this. Now check for the ID in the
+Graphics constructor and then print the stacktrace.
+
+However I don't get any X11 errors anymore so I can't test it :(.