JDK-8277573 : VmObjectAlloc is not generated by intrinsics methods which allocate objects
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 18,19
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2021-11-22
  • Updated: 2022-11-18
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.
Other
tbdUnresolved
Related Reports
Duplicate :  
JDK-8277812 - vmTestbase/nsk/jvmti/AttachOnDemand/attach002a/TestDescription.java fails with "TestFailure: InterruptedException.getMessage() returns unexpected value (expected is 'attach002a: redefined version'), probably class wasn't redefined"
Relates :  
JDK-8288430 - serviceability/jvmti/VMObjectAlloc/VMObjectAllocTest.java failed with "Exception: Number of allocation != 1"
Sub Tasks
JDK-8287877 :  
Exclude vmTestbase/nsk/jvmti/AttachOnDemand/attach022/TestDescription.java until JDK-8277573 is fixed - Resolved
Description
While fixing https://bugs.openjdk.java.net/browse/JDK-8265795 I noticed that event is not posted in the intrinsics version for many functions where it is used. Including but not limited to clone(), invoke()m allocateInstance() and allocateUninitializedArray(). There are might be other intensified functions (not analogs JVM_ENTRY versions) that allocate objects without post events.

Here is the comment from David H.
"
I agree that fixing intrinsics should be a separate issue - I have to worry that the overhead of posting events can dwarf the operation itself. I would guess the intrinsic would need a short-cut to check if the event is enabled and if so drop back to non-intrinsic version.
"