[SERVER-6444] when time (ticks) go backwards Timer overflows Created: 13/Jul/12 Updated: 10/Dec/14 Resolved: 01/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | buildbot, waiting_for_review | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
... which can be a problem on VMs. This leads to huge values being reported in seconds/millis/minutes when the unsigned micros() value gets converted to signed integer values. Potential solution - signed ticks? We should also warn the user when this is potentially detected now() - old > 1/2 the range. |