8306992: [JVMCI] mitigate more against JVMCI related OOME causing VM to exit#13905
8306992: [JVMCI] mitigate more against JVMCI related OOME causing VM to exit#13905dougxc wants to merge 5 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back dnsimon! A progress list of the required criteria for merging this PR into |
| ResourceMark rm(thread); | ||
| JavaThreadState state = JavaThread::cast(thread)->thread_state(); | ||
| if (state == _thread_in_vm || state == _thread_in_Java || state == _thread_new) { | ||
| tty->print("JVMCITrace-%d[%s]:%*c", level, thread->name(), level, ' '); |
There was a problem hiding this comment.
This change helps correlate threads in a trace that transition in and out of libgraal (thread name is not available when in libgraal).
Webrevs
|
|
@dougxc This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 4 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
|
@dougxc Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information. |
|
I rebased this PR to remove commits from #14000 that accidentally got cherry-picked into this PR. |
|
@tkrodriguez could you please review fb22509 which I added to handle cases such as oracle/graal#6216 (comment). |
|
I think the new changes look ok. |
| MutexLocker locker(_lock); | ||
| JavaVM* javaVM = _shared_library_javavm; | ||
| if (javaVM == nullptr) { | ||
| const char* val = Arguments::PropertyList_get_value(Arguments::system_properties(), "test.jvmci.forceEnomemOnLibjvmciInit"); |
There was a problem hiding this comment.
Note that this view on system properties is restricted to properties set at VM startup (e.g. on the command line) and will not see the result of calls to System.setProperty() made by an application.
|
Thanks for the reviews @tkrodriguez . /integrate |
|
Going to push as commit 422128b.
Your commit was automatically rebased without conflicts. |
This PR makes the following changes to mitigate against an OOME or other recoverable error in JVMCI from causing the VM to exit:
When JVMCI compilation is disabled, a warning is emitted:
With
-Xlog:jit+compilation, the extra detail shown is:Note that the errors treated by the changes in the PR are expected to be exceedingly rare. For example, an OOME while starting a libgraal isolate or initializing the JVMCI compiler. Exceptions thrown during compilation are already handled by the Graal CompilationWrapper.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/13905/head:pull/13905$ git checkout pull/13905Update a local copy of the PR:
$ git checkout pull/13905$ git pull https://git.openjdk.org/jdk.git pull/13905/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 13905View PR using the GUI difftool:
$ git pr show -t 13905Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/13905.diff
Webrev
Link to Webrev Comment