[concurrency-interest] Sleep time consistency compared to System.currentTimeMillis

Carl Mastrangelo notcarl at google.com
Mon Aug 27 13:23:45 EDT 2018


That's good to hear it was a bug.  I had asked about in on Stack Overflow*
a while ago, and no one seemed to recognize it should be fixed.


*
https://stackoverflow.com/questions/42544387/why-does-thread-join-use-currenttimemillis


On Mon, Aug 27, 2018 at 7:06 AM Martin Buchholz via Concurrency-interest <
concurrency-interest at cs.oswego.edu> wrote:

> Thread.jjoin(long) should be fixed to use nanoTime instead of
> currentTimeMillis.
>
> Thread.wait's spec should be fixed to remove the "more or less" (although
> spurious wakeup remains possible).
>
> Thread.sleep should be fixed to not wake up early due to rounding of nanos
> (as Object.wait was fixed).
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20180827/a042c5fe/attachment.html>


More information about the Concurrency-interest mailing list