JDK-8208249 : TriggerUnloadingByFillingMetaspace generates garbage class names
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-07-26
  • Updated: 2022-03-09
  • Resolved: 2018-08-02
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
11.0.16-oracleFixed 12 b06Fixed
Related Reports
Relates :  
JDK-8158168 - Missing bounds checks for some String intrinsics
Description
test/hotspot/jtreg/vmTestbase/vm/share/gc/TriggerUnloadingByFillingMetaspace.java uses a shared  GeneratedClassProducer between 30 threads.  The  GeneratedClassProducer generates class name strings using an unsynchronized StringBuilder.  This results in garbage class names being generated and exceptions being thrown.
Comments
Fix request [11u] I backport this for parity with 11.0.16-oracle. No risk, only a test change. Clean backport. SAP nightly testing passed.
08-03-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk11u-dev/pull/858 Date: 2022-03-07 16:51:41 +0000
07-03-2022
Git URL: https://github.com/openjdk/jdk/commit/3d94ce71b5c379627406b3c889058d49bd5b7622
07-03-2022
URL: http://hg.openjdk.java.net/jdk/jdk/rev/3528ba05663a User: tschatzl Date: 2018-08-02 10:29:01 +0000
02-08-2018