> > There are few things to watch for: > - make sure the pool (from which the timer entry is allocated from) > remains valid until the timer expires > - make sure the timer is not currently being scheduled before you > re-schedule it (you can use timer.id field for this purpose). > - although timer heap object is thread safe, access to your timer > entry is not (e.g., registration callback may be called while you're > processing a timer callback). So make sure your application protects > access to the timer entry where required. > First 2 points were my problem. Thanks a lot for the help. -Anshuman
