-
Bug
-
Resolution: Fixed
-
P4
-
hs25
-
b24
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8056618 | emb-9 | Unassigned | P4 | Resolved | Fixed | b24 |
While the review for JDK-8016270 was being done, it was noted that there are some places where codecache allocation failures are detected, but they do not trigger invoking the sweeper by calling CompileBroker::handle_full_code_cache().
For example, Compile::init_buffer() and several other similar places in output.cpp:
// Have we run out of code space?
if ((cb->blob() == NULL) || (!CompileBroker::should_compile_new_jobs())) {
C->record_failure("CodeCache is full");
return NULL;
}
And in Compile::init_scratch_buffer_blob():
if (scratch_buffer_blob() == NULL) {
// Let CompilerBroker disable further compilations.
record_failure("Not enough space for scratch buffer in CodeCache");
return;
}
For example, Compile::init_buffer() and several other similar places in output.cpp:
// Have we run out of code space?
if ((cb->blob() == NULL) || (!CompileBroker::should_compile_new_jobs())) {
C->record_failure("CodeCache is full");
return NULL;
}
And in Compile::init_scratch_buffer_blob():
if (scratch_buffer_blob() == NULL) {
// Let CompilerBroker disable further compilations.
record_failure("Not enough space for scratch buffer in CodeCache");
return;
}
- backported by
-
JDK-8056618 Some codecache allocation failures don't result in invoking the sweeper
- Resolved
- relates to
-
JDK-8016270 "CodeCache is full" message and compilation disabled, but codecache is not actually full
- Closed