JDK-8318563 : GetClassFields should not use random access to field
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 21.0.2,22,23
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • CPU: generic
  • Submitted: 2023-10-19
  • Updated: 2024-01-18
  • Resolved: 2024-01-12
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 23
23 b06Fixed
Related Reports
Blocks :  
JDK-8317635 - Improve GetClassFields test to verify correctness of field order
Blocks :  
JDK-8317692 - jcmd GC.heap_dump performance regression after JDK-8292818
Relates :  
JDK-8317635 - Improve GetClassFields test to verify correctness of field order
Relates :  
JDK-8317692 - jcmd GC.heap_dump performance regression after JDK-8292818
Description
This is follow-up for JDK-8317692
GetClassFields JVMTI function uses FilteredFieldStream from reflectionUtils.hpp which iterates fields in the reverse order and is known to be performance ineffective (see JDK-8317692 for details).
Comments
Changeset: 84cf4cb3 Author: Alex Menkov <amenkov@openjdk.org> Date: 2024-01-12 20:41:49 +0000 URL: https://git.openjdk.org/jdk/commit/84cf4cb350331aac147fdf4c6d130cdf5448c987
12-01-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17094 Date: 2023-12-13 21:32:50 +0000
13-12-2023