-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8293872: Make runtime/Thread/ThreadCountLimit.java more robust #10290
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
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
dholmes-ora
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine. Thanks.
|
@shipilev 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 134 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thanks! Can I have another review? |
Ping? |
adinn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
|
Thank you! /integrate |
|
Going to push as commit 36b61c5.
Your commit was automatically rebased without conflicts. |
I am seeing this failure frequently on linux-x86:
It usually crashes when it tries to do heavy stuff in
OutOfMemoryErrorblock, which ends up either allocating the metadata for string concat method handles (the most frequent case), or allocating memory for resulting Strings. Sometimes even the threads themselves end up receiving a secondary OOM after main loop catches it.I think we can strengthen this test significantly, by avoiding unnecessary things in dangerous loops.
Additionally, since the test can foobar the VM and/or experience heap memory runaway, it needs to run with othervm and fixed heap size.
After JDK-8255450, this test still runs in tier2.
Additional testing:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10290/head:pull/10290$ git checkout pull/10290Update a local copy of the PR:
$ git checkout pull/10290$ git pull https://git.openjdk.org/jdk pull/10290/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10290View PR using the GUI difftool:
$ git pr show -t 10290Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10290.diff