[GR-36433] Execute shutdown hooks on JNI DestroyJavaVM.#13841
Merged
Conversation
oracle-contributor-agreement
Bot
added
the
OCA Verified
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Execute shutdown hooks on JNI
DestroyJavaVMand ignore exceptions, like HotSpot does. We have run startup hooks forCreateJavaVMby default for a while. Startup and shutdown hooks are also always executed with an executable image built for a Java main method.Note that there's also initialization hooks and tear-down hooks. These are unconditionally invoked on isolate creation and initialization. Startup and shutdown hooks, however, must be invoked explicitly with custom entry points via
VMRuntime.initializeandVMRuntime.shutdown(done by libgraal, for example).