Skip to content
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

Show 0 for MaxDirectMemorySize with PrintFlagsFinal when unset #16639

Merged
merged 1 commit into from
Feb 7, 2023

Conversation

pshipton
Copy link
Member

Fixes #16637

java -XX:+PrintFlagsFinal

[Global flags]
   size_t MaxHeapSize                              = 2083651584                                {product} {ergonomic}
 uint64_t MaxDirectMemorySize                      = 0                                         {product} {ergonomic}

runtime/vm/jvminit.c Outdated Show resolved Hide resolved
runtime/jcl/common/system.c Outdated Show resolved Hide resolved
runtime/vm/jvminit.c Outdated Show resolved Hide resolved
Issue eclipse-openj9#16637

Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
@pshipton
Copy link
Member Author

pshipton commented Feb 1, 2023

Fixed the brackets.

@keithc-ca
Copy link
Contributor

Jenkins test sanity alinux64 jdk11

@keithc-ca keithc-ca merged commit be89be0 into eclipse-openj9:master Feb 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MaxDirectMemorySize memory size reported by -XX:+PrintFlagsFinal is incorrect (i.e it's -1 by default)
2 participants