JDK-8071864 : compiler/c2/6772683/InterruptedTest.java failed in nightly
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8u112,9
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2015-01-29
  • Updated: 2017-07-26
  • Resolved: 2016-01-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b105Fixed
Related Reports
Relates :  
JDK-6772683 - Thread.isInterrupted() fails to return true on multiprocessor PC
Description
----------System.out:(19/879)----------
Main thread: starts a worker thread...
Main thread: waits at most 5s for the worker thread to die...
Worker thread: running...
Main thread: interrupts the worker thread...
Main thread: worker thread is interrupted
Main thread: waits for the worker thread to die...
Main thread: interrupts the worker thread...
Main thread: worker thread is interrupted
Main thread: waits for the worker thread to die...
Main thread: interrupts the worker thread...
Main thread: worker thread is interrupted
Main thread: waits for the worker thread to die...
Main thread: interrupts the worker thread...
Main thread: worker thread is interrupted
Main thread: waits for the worker thread to die...
Main thread: interrupts the worker thread...
Main thread: worker thread is interrupted
Main thread: waits for the worker thread to die...
Main thread: the worker thread dod not die
Comments
verified by nightly testing
26-07-2017
Reopening because I'd like to propose a fix that updates the test.
13-01-2016
The failure has appeared two times. In both cases, the failure appeared on Windows with a fastdebug x86_32 build. Both failures happened on the same x86_64 machine running Windows 7 Enterprise. The VM was running in two different configurations (set of flags) when the two failures have appeared: Configuration #1: -server -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -ea -esa -XX:+TieredCompilation -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions Configuration #2: -client -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -XX:NativeMemoryTracking=detail -XX:ReservedCodeCacheSize=256M The failure appears with both the client and the server VM, therefore it can't be specific to the C2 compiler (and is not related to JDK-6772683). The failure is related to thread interruption (the API defined in java.lang.Thread). The C1 compiler does not intrinsify any of the methods in java.lang.Thread, so we can exclude the cause of the problem being related to compiler intrinsics. I attempted to reproduce the failure on two machines, M1 and M2. M1 is the machine where both failures reported in this issue happened. I used both configurations. The failure did not reproduce. Here are number of executions of the reproducer in each configuration and on each machine: M1/Configuration 1: 1'200 M2/Configuration 1: 1'600 M1/Configuration 2: 6'000 M2/Configuration 2: 9'000. As the failure has appeared on a single Windows machine, M1, I suspect the problem to be related to the machine or that configuration of Windows. I will close this issue as "Cannot reproduce". If the failure occurs again, please reopen the issue, but only if the machine where the failure has appeared is different than M1.
12-01-2016
Tried to reproduce the bug (same machine, same binary) without success. Since this is the first occurrence of this error, it could also very well be an environment issue. I suggest to close this for now.
02-02-2015
[~kvn] pushed the test as part of JDK-6772683.
30-01-2015
I'm not sure if this is a compiler bug.
29-01-2015