-
Bug
-
Resolution: Fixed
-
P5
-
11, 12, 13, 14
-
b24
CompileBroker::possibly_add_compiler_threads() contains usage of the macro "CHECK" which contains a return statement (in case of exception).
This should never happen, but if it did, returning would mess things up (e.g. CompileThread_lock doesn't get unlocked).
This should never happen, but if it did, returning would mess things up (e.g. CompileThread_lock doesn't get unlocked).
- relates to
-
JDK-8198756 Lazy allocation of compiler threads
- Resolved