Add debug option to force GPF on heap initialization error #18345
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is kind of the problem Service observes often - an attempt to launch JVM is failed due Object Heap initialization error. For example there are multiple cases for Windows users trying to use harge heaps with Compressed Refs JVM. Generation of system core for investigation is problematic because this failure occurs very early in JVM startup. Adding debug non-published option -XXgc:forceGPFOnHeapInitializationError to help Service investigate this kind of the problem. Signed-off-by: Dmitri Pivkine <[email protected]>
amicic
approved these changes
Oct 25, 2023
|
jenkins test sanity aix,win jdk17 |
|
seems like an infra failure on AIX, but still, i'll try again... |
|
jenkins test sanity aix jdk11 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is kind of the problem Service observes often - an attempt to launch JVM is failed due Object Heap initialization error. For example there are multiple cases for Windows users trying to use harge heaps with Compressed Refs JVM. Generation of system core for investigation is problematic because this failure occurs very early in JVM startup. Adding debug non-published option
-XXgc:forceGPFOnHeapInitializationError to help Service investigate this kind of the problem.