Virtual threads and bug in CompletableFuture.get(timeout,unit)

Alan Bateman Alan.Bateman at oracle.com
Tue Jul 14 14:33:30 UTC 2020


On 14/07/2020 15:21, Bela Ban wrote:
> I'm consistently running into the problem that a timed 
> get(timeout,unit) on CompletableFuture (see stack trace below) blocks 
> for *up to timeout millis* although complete(result) has been called.
>
> If I use the non-timed CompletableFuture.get(), this always works: the 
> get() method returns as soon as complete() has been called.
>
> I'm trying to put together a reproducer.
>
> Are there any known issues with the timed in 
> CompletableFuture.get(timeout,unit) / VirtualThread.parkNanos() in 
> Loom (16-loom+2-14)?
I can't think of any issues in this area. It would be great if can 
create a reproducer.

-Alan


More information about the loom-dev mailing list