The SampledObjectAlloc event is called before object is cloned. It might potentially cause the issues because Clone() implementation might rely on the fact that object is not updated before creation an updating by clone.
The proposed fix is to call SampledObjectAlloc after clone is completed like it is done for VMObjectAlloc. Thus clone is atomic and can't be interrupted by Java code. The JVMTI specification is not specific to the exact time when the event is called. --------- - [x] I confirm that I make this contribution in accordance with the [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). ------------- Commit messages: - removed import Changes: https://git.openjdk.org/jdk/pull/33483/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=33483&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8383787 Stats: 175 lines in 2 files changed: 175 ins; 0 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/33483.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/33483/head:pull/33483 PR: https://git.openjdk.org/jdk/pull/33483
