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=78052 --- shadow/78052 2006-08-26 09:48:16.000000000 -0400 +++ shadow/78052.tmp.9939 2006-08-26 17:08:32.000000000 -0400 @@ -1,13 +1,13 @@ Bug#: 78052 Product: Mono: Class Libraries Version: unspecified OS: unknown OS Details: -Status: ASSIGNED -Resolution: +Status: RESOLVED +Resolution: FIXED Severity: Unknown Priority: Normal Component: Windows.Forms AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -70,6 +70,13 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-08-26 09:48 ------- I think peter pretty much figured it out last night. The issue seems to happen when the form is in the same message loop as the popped up form, and has been closed. So it likely has something to do with our destruction code. + +------- Additional Comments From [EMAIL PROTECTED] 2006-08-26 17:08 ------- +This happened due to a bad assumption on my part two years ago, when +I wrote the toplevel close handler in X11. For safety, I wiped out +the System.Drawing Display handle when the window was closed. I +missed that there might be more than one toplevel window the app has. +Fixed in svn r64415. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
