-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[GR-67262] Fix JFR GC events. #11570
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
checkstyle fix small bug
cf4c3b2 to
448c06b
Compare
e579446 to
448c06b
Compare
|
Thanks, will be integrated in the next few days. |
| @@ -0,0 +1,69 @@ | |||
| /* | |||
| * Copyright (c) 2022, 2022, Oracle and/or its affiliates. All rights reserved. | |||
| * Copyright (c) 2022, 2022, Red Hat Inc. All rights reserved. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will change the copyright years of this file to 2025 if this is fine with you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please! I forgot to update that. Thanks
|
@christianhaeubl should I now open a backport PR to the GraalVM for JDK25 release branch? |
|
Not necessary, I already did that (but may take a few days until it gets merged and therefore mirrored to GitHub). |
We are currently writing JFR
jdk.GarbageCollectionevents incorrectly. The event format has an "event thread" data field, but we are not writing it. This causes the subsequent fields to have incorrect placement and be written wrong as well.Before the fix: notice many fields are blank or zero


After the fix:
I've added a test to catch such issues in the future.
This bug affects the GraalVM for JDK 25 release branch (https://github.com/oracle/graal/tree/release/graal-vm/25.0) as well and should be backported to it.