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

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Sep 28 08:33:12 EDT 2008


User awunwpa7 at yahoo.com.ph added comment

           Summary: Timer.OnTimer() function got called with non-gui thread
           Product: Mono: Class Libraries
           Version: 2.0
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Windows.Forms
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: awunwpa7 at yahoo.com.ph
         QAContact: mono-bugs at lists.ximian.com
          Found By: Beta-Customer

Description of Problem:

It seems to be possible in MONO that the OnTimer function of a Timer is not
called by the gui thread, but by some other thread. As the OnTimer function
usually operates on winform controls, a wrong thread might easily lead to
threadding trouble.

To prevent this, the MS framework normally throws an InvalidOperationException
as soon as a wrong thread touches anything. Instead the MONO framework does not
seem to care much and lets strange threads operate on the gui controls without
any worrying. This is normally not a problem, but can lead to one if a wrong
thread appears in a context where you don't assume it (for example in the
OnTimer function). I suppose the MONO winform controls are not thread safe for
such situations.

See second comment of bug #430477 for how I found this one. Found with MONO 2.0
rc1 on WinXP.

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