Fix runaway thread explosion when ForkJoinPool parallelism is < 2 #43
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.
covers has observed in the wild that the installer may create a runaway number of threads (thousands upon thousands).
The analysis has shown that this is the case in java < 25 if the common ForkJoinPool has parallelism of less than 2. In that case, CompletableFuture#runAsync using that pool will fall back to use one thread per submitted task.
Since we submit tasks for every class in the game at once, that will lead to this issue.
The solution is to detect this and use a dedicated worker thread instead, which is also what Java 25 does.
See: https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html