-
Bug
-
Resolution: Fixed
-
P2
-
7u80, 9
-
b13
-
os_x
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8045438 | 8u25 | Staffan Larsen | P2 | Resolved | Fixed | b01 |
JDK-8040640 | 8u20 | Staffan Larsen | P2 | Closed | Fixed | b15 |
JDK-8053356 | emb-8u26 | Staffan Larsen | P2 | Resolved | Fixed | b17 |
The current implementation of System.nanoTime() on OS X uses gettimeofday() which has only microsecond precision and no guarantees on being monotonic.
- backported by
-
JDK-8045438 System.nanoTime() is slow and non-monotonic on OS X
-
- Resolved
-
-
JDK-8053356 System.nanoTime() is slow and non-monotonic on OS X
-
- Resolved
-
-
JDK-8040640 System.nanoTime() is slow and non-monotonic on OS X
-
- Closed
-
- duplicates
-
JDK-8040254 Garbage Collection on MacOSX can crash in fastdebug because of 'negative time'
-
- Closed
-
- relates to
-
JDK-8040254 Garbage Collection on MacOSX can crash in fastdebug because of 'negative time'
-
- Closed
-
-
JDK-6864866 add a flag to use result of gethrtime() directly in os::getTimeNanos() on Solaris and OS X
-
- Closed
-
(1 relates to)