JDK-8210511 : TestSingleWriterSynchronizer can deadlock
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2018-09-07
  • Updated: 2018-09-12
  • Resolved: 2018-09-10
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 12
12 b11Fixed
Related Reports
Relates :  
JDK-8209850 - Allow NamedThreads to use GlobalCounter critical sections
Description
The gtest for SingleWriterSynchronizer can deadlock:

utilities/test_singleWriterSynchronizer.cpp

* The synchronization test threads are doing their thing while waiting for continue_running to be flipped to 0.
* The gtest launcher thread that kicked them off is in os::sleep, and can perform a safepoint poll. It will never set continue_running to 0 until the safepoint is over.
* The VM thread is synchronizing a safepoint, waiting for the synchronization test threads to yield to the safepoint, but they do not have any safepoint polls in their loops, and will stall the safepoint indefinitely.