[Mono-bugs] [Bug 558652] New: Timer stops calling callback after timer.Change() was called

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=558652

http://bugzilla.novell.com/show_bug.cgi?id=558652#c0


           Summary: Timer stops calling callback after timer.Change() was
                    called
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x AddOn CD
          Platform: x86-64
        OS/Version: SLES 11
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: CORLIB
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: witold.szymaniak at secpl.cs.put.poznan.pl
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=329613)
 --> (http://bugzilla.novell.com/attachment.cgi?id=329613)
Test case

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.11 Safari/532.5

Setting timer to run after selected period makes callback to be called. When,
inside the callback, timer is set up again the callback is never called and
whole system hangs. I've tested it on several platforms

SLES11 + Mono Extension - hangs
Debian + Mono 2.4.2.3 - sometimes hangs, sometimes runs
Debiang + Mono Trunk - hangs
Windows + .NET - runs
Windows + Mono - runs (!!!)

Reproducible: Sometimes

Steps to Reproduce:
1. Initialize timer and set it to run only once
2. In the callback, set the timer again
3. Bang! The callback is not called (happens very often).
Actual Results:  
Bang! The callback is not called

Expected Results:  
Callback is called again

Attached testcase that reproduces the problem

-- 
Configure bugmail: http://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.