[Mono-bugs] [Bug 78823][Nor] Changed - Application.Idle called once per thread instead of 1 time only

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Sep 27 20:26:29 EDT 2006

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 toshok at ximian.com.


--- shadow/78823	2006-09-27 05:12:11.000000000 -0400
+++ shadow/78823.tmp.825	2006-09-27 20:26:29.000000000 -0400
@@ -3,20 +3,20 @@
 Version: 1.1
 OS: other
 OS Details: Ubuntu
 Status: ASSIGNED   
 Severity: Unknown
-Priority: Blocker
+Priority: Normal
 Component: Windows.Forms
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: roger.jakobsson at jorosoft.se               
 QAContact: toshok at ximian.com
 TargetMilestone: 1_2
-Summary: Splash implementation hangs
+Summary: Application.Idle called once per thread instead of 1 time only
 BugsThisDependsOn: 79196, 79217[FIXED]
 Description of Problem:
 This splash screen implementation hangs mono completely.
 Steps to reproduce the problem:
@@ -166,6 +166,14 @@
 Our X implementation fires it twice, because both forms end up in
 UpdateMessageQueue, and each fire an Idle event.
 This is probably unfixable in the short term, as I can't think of a
 way we can reliably emit it only once, without having a separate
 thread handling all the X event loop stuff.
+------- Additional Comments From toshok at ximian.com  2006-09-27 20:26 -------
+all the crashes and hangs that I can find have been fixed.  the only
+remaining issue with this bug is the Application.Idle problem (it's
+being emitted once per thread instead of one time).
+I'm going to downgrade this to Normal and change the subject to
+reflect this.

More information about the mono-bugs mailing list