[Mono-bugs] [Bug 414199] New: OpenFileDialogs / SaveFileDialogs freezing applications without MONO_MWF_MAC_FORCE_X11 set
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Sun Aug 3 14:25:30 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=414199
Summary: OpenFileDialogs / SaveFileDialogs freezing applications
without MONO_MWF_MAC_FORCE_X11 set
Product: Mono: Class Libraries
Version: 2.0
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Windows.Forms
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: fbergman at u.washington.edu
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Created an attachment (id=231415)
--> (https://bugzilla.novell.com/attachment.cgi?id=231415)
sample assembly exhibiting the problem
Description of Problem:
Trying out the pre-release version of Mono 2.0 on OSX 10.5 i find most of my
applications freezing when they try to open a openfiledialog. The problem
disappears if X11 is chosen as rendering system by setting
MONO_MWF_MAC_FORCE_X11=1 prior to launching the application.
Unfortunately trivial applications do not show the same problem though a crash
still appears and it works with X11, but not without, so they might be related
Steps to reproduce the problem:
1. start the attached assembly OpenFileDialogTest.exe from Terminal with mono
OpenFileDialogTest.exe
Actual Results:
when clicking the "open" button the application crashes with:
$ mono ~/Desktop/OpenFileDialogTest.exe
Unhandled Exception: System.ArgumentException: Forms cannot own themselves or
their owners.
Parameter name: owner
at System.Windows.Forms.Form.ShowDialog (IWin32Window owner) [0x00000]
at (wrapper remoting-invoke-with-check) System.Windows.Forms.Form:ShowDialog
(System.Windows.Forms.IWin32Window)
at System.Windows.Forms.CommonDialog.ShowDialog (IWin32Window owner)
[0x00000]
at System.Windows.Forms.CommonDialog.ShowDialog () [0x00000]
at (wrapper remoting-invoke-with-check)
System.Windows.Forms.CommonDialog:ShowDialog ()
at OpenFileDialogTest.Form1.cmdOpen_Click (System.Object sender,
System.EventArgs e) [0x00000]
at System.Windows.Forms.Control.OnClick (System.EventArgs e) [0x00000]
at System.Windows.Forms.Button.OnClick (System.EventArgs e) [0x00000]
at System.Windows.Forms.ButtonBase.OnMouseUp
(System.Windows.Forms.MouseEventArgs mevent) [0x00000]
at System.Windows.Forms.Button.OnMouseUp (System.Windows.Forms.MouseEventArgs
mevent) [0x00000]
at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m)
[0x00000]
at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m)
[0x00000]
at System.Windows.Forms.ButtonBase.WndProc (System.Windows.Forms.Message& m)
[0x00000]
at System.Windows.Forms.Button.WndProc (System.Windows.Forms.Message& m)
[0x00000]
at System.Windows.Forms.Control+ControlWindowTarget.OnMessage
(System.Windows.Forms.Message& m) [0x00000]
at System.Windows.Forms.Control+ControlNativeWindow.WndProc
(System.Windows.Forms.Message& m) [0x00000]
at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr
wParam, IntPtr lParam) [0x00000]
at System.Windows.Forms.XplatUICarbon.DispatchMessage
(System.Windows.Forms.MSG& msg) [0x00000]
at System.Windows.Forms.XplatUI.DispatchMessage (System.Windows.Forms.MSG&
msg) [0x00000]
at System.Windows.Forms.Application.RunLoop (Boolean Modal,
System.Windows.Forms.ApplicationContext context) [0x00000]
at System.Windows.Forms.Application.Run
(System.Windows.Forms.ApplicationContext context) [0x00000]
at System.Windows.Forms.Application.Run (System.Windows.Forms.Form mainForm)
[0x00000]
at OpenFileDialogTest.Program.Main () [0x00000]
when running the application again using:
$ MONO_MWF_MAC_FORCE_X11=1 mono ~/Desktop/OpenFileDialogTest.exe
the application works without problems.
Expected Results:
same behavior whether X11 is being used or Carbon is being used
How often does this happen?
always
Additional Information:
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list