[Mono-bugs] [Bug 75765][Nor] Changed - Mono 1.1.8.3 - iFolder 3 client/Simias process doesn't shutdown properly with this version of mono

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Aug 25 17:37:11 EDT 2005


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 mlasky at novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75765

--- shadow/75765	2005-08-18 14:26:02.000000000 -0400
+++ shadow/75765.tmp.8105	2005-08-25 17:37:10.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 75765
 Product: Mono: Runtime
 Version: 1.1
 OS: NLD 9
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: ifolder.guy at gmail.com               
 QAContact: mono-bugs at ximian.com
@@ -43,6 +43,23 @@
 ------- Additional Comments From jpallen at novell.com  2005-08-18 14:24 -------
 *** Bug 75473 has been marked as a duplicate of this bug. ***
 
 ------- Additional Comments From jpallen at novell.com  2005-08-18 14:26 -------
 Please note that we saw a similar problem months ago, but it was fixed
 for us in our stable 1.1.7 branch.  It looks like it is back with 1.1.8.
+
+------- Additional Comments From mlasky at novell.com  2005-08-25 17:37 -------
+This was a problem with the iFolderClient application. The simias 
+mono process was going away cleanly every time. The iFolderClient 
+code was spinning up a foreground thread which would block for two 
+seconds and then call EnvironmentExit. This code was used to get 
+around intermittent shutdown problems with mono version 1.1.7. On 
+mono version 1.1.8, the mono process would not go away because this 
+foreground thread was either running or queued to run when the main 
+thread called Application.Exit(). Changing to a background thread 
+allowed the appdomain to terminate the thread and cleanly exit the 
+program.
+
+It is possible that there is some deadlock between the foreground 
+thread create/run and the Application.Exit() on mono 1.1.8 and this 
+should be looked into further. But, for the purposes of this bug, it 
+is fixed.


More information about the mono-bugs mailing list