This question is locked. New answers and comments are not allowed.
Hi,
Our test department have found a crash in Equatec library code (.Net).
It's not anything critical but I believe it'd be nice to have fixed. What they do is basically fiddle with system time settings (setting it back and forth to +40 days, +60 days and +30 years) - this is an automated test. It happens that our application goes down because of the analytics library (startup) here is the stack-trace.
This is barely possible scenario but it's annoying for our Test Department. Could you put some range checks before calling to the Timer.Change call? (do you base it on the system time?) are there any other surprises that we should expect when changing system time ?
Regards,
Lukasz
1 Answer, 1 is accepted
0
Guest
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2012, 03:21 PM
Hi Peter and Lukasz,
Thanks for reporting this.
It really does seem to be a bug in our .NET monitor. If the system time is adjusted radically, as in your example, our code does not honor the requirement by time-changes to s system Timer to be 4294967294 msec or less. Our mistake.
We have fixed the bug now (it was in two places in the code) and it will be part of the next release of the .NET monitor. There are no other surprises that I know of now. We will let you know where there is a new release of the monitor library, and will attempt to make a new release as soon as possible.
Thanks again for this fine bug report.
best regards,
Richard Flamsholt
EQATEC Team