On Wed, 21 Oct 2026 01:39:57 GMT, Leonid Mesnik <[email protected]> wrote:
>> 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). > > Leonid Mesnik has updated the pull request incrementally with one additional > commit since the last revision: > > the fix In the current code where is the event generated? I don't see how the change here moves the event generation site. I also wonder whether there could be any compatibility implications with this change in behaviour? ------------- PR Comment: https://git.openjdk.org/jdk/pull/33483#issuecomment-6326095174 PR Comment: https://git.openjdk.org/jdk/pull/33483#issuecomment-6326110204
