JDK-8217378 : UseCriticalCMSThreadPriority is broken
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 11,12,13
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-01-18
  • Updated: 2019-09-06
  • Resolved: 2019-01-19
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 11 JDK 12 JDK 13
11.0.3Fixed 12.0.2Fixed 13 b05Fixed
Related Reports
Blocks :  
JDK-8217343 - Shenandoah control thread should be able to run at critical priority
Relates :  
JDK-7091418 - FX priority class from Solaris should be available to JVM
Relates :  
JDK-8140257 - Add support for "gc service threads" to ConcurrentGCThread
Description
See, for example:

$ build/linux-x86_64-server-fastdebug/images/jdk/bin/java -XX:+UseConcMarkSweepGC -XX:+UnlockExperimentalVMOptions -XX:+UseCriticalCMSThreadPriority
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc:  SuppressErrorAt=/os.cpp:224
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (/home/shade/trunks/jdk-jdk/src/hotspot/share/runtime/os.cpp:224), pid=18502, tid=18503
#  assert(false) failed: Should not happen
#
# JRE version:  (13.0) (fastdebug build )
# Java VM: OpenJDK 64-Bit Server VM (fastdebug 13-internal+0-adhoc.shade.jdk-jdk, mixed mode, aot, sharing, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x14e23ca]  os::set_priority(Thread*, ThreadPriority)+0x3a
#
Comments
Fix Request This resolves the regression introduced in 9. The risk is minimal to none. The patch applies cleanly to both 11u and 12u, and passes the new regression test.
06-02-2019
I'm good with where it is.
18-01-2019
Fix is in (shared) runtime code. I have no preference, please move if you think it belongs in hotspot/gc.
18-01-2019
Shouldn't this be in hotspot/gc instead of hotspot/runtime?
18-01-2019
This got broken by JDK-8140257.
18-01-2019
RFR: http://mail.openjdk.java.net/pipermail/hotspot-dev/2019-January/036314.html
18-01-2019