-
Notifications
You must be signed in to change notification settings - Fork 114
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
Add -Xalwaysclassgc to Test5102804 #849
base: openj9
Are you sure you want to change the base?
Conversation
Please run in Grinder and add ibm license. |
- Updated the @run with -Xalwaysclassgc jvm option - This is a temporary workaround and should be reviewed once the root cause is identified. related: eclipse-openj9/openj9#20531 Signed-off-by: Anna Babu Palathingal <[email protected]>
Grinder run:
|
I'm not sure this is a solution, just a temporary workaround, which we should call out in the commit description. |
Also, this change should start at the openjdk head stream (openj9-openjdk-jdk) and then be backported to 23, 21, 17, and then 11. Unless for some reason it only fails on 11? |
0fc6844
to
644a18c
Compare
Well, I have a plan to find out exact scenario. However I don't think there is something wrong with handling. This is combination class unloading - > clearing Weak Ref. OpenJ9 does not do class unloading every time. It does it for aggressive GC to prevent OOM but it is too late to process Weak Ref. If you need this test pass without pushing class unloading every single Global GC an alternative can be to have another run of aggressive Global GC. I am not sure it is necessary. |
Continuing the discussion in eclipse-openj9/openj9#20531 (comment) |
Based on the current results , The test: |
related: eclipse-openj9/openj9#20531