[Mono-bugs] [Bug 430483] Timer.OnTimer() function got called with non-gui thread

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sat Oct 11 13:14:21 EDT 2008


User awunwpa7 at yahoo.com.ph added comment

Steve Odbc <awunwpa7 at yahoo.com.ph> changed:

           What    |Removed                                         |Added
             Status|NEEDINFO                                        |NEW
      Info Provider|awunwpa7 at yahoo.com.ph                           |

--- Comment #11 from Steve Odbc <awunwpa7 at yahoo.com.ph>  2008-10-11 11:14:20 MDT ---
Created an attachment (id=244985)
 --> (https://bugzilla.novell.com/attachment.cgi?id=244985)
Stacktrace of exception

Your code (id=244405) tested on WinXP.

With the MS framework 3.5 SP1, I saw the "Fail()..." message box and the five
timer message boxes, then everything disappeared. This seems to be the correct
behavior of the code.

With the MONO framework 2.0 final release, I saw the "Fail()..." message box
and one timer message box, then everything disappeared.

I re-excuted and this time MONO quitted within very small time, I only saw the
shape of the form appearing, then it disappered. This also happend when I
re-executed a second and a third time.

It seems that the statement

if (UiTag == null) Environment.Exit (1);

is NOT responsible for MONO's fast exit. So this test case didn't reproduce the
second bug, but the first bug (see my previous comment).

Then I executed your code with the "--debug" runtime flag on MONO. This time
(for the first time at all) the code seemed to work flawless on MONO. Then I
re-excuted and ran into a MemberAccessException very soon. The stack trace is
attached. This is the whole story behind the first bug, I suppose.

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