Java
Object allocation in loop
Warning
New
Last modified: 03 December 2024Reports object or array allocations inside loops. While not necessarily a problem, an object allocation inside a loop is a great place to look for memory leaks and performance issues.
The inspection reports the following constructs:
Explicit allocations via
new
operatorMethods known to return new object
Instance-bound method references
Lambdas that capture variables or
this
reference
Example:
// Explicit allocation
for (Status status : Status.values()) {
declarationsMap.put(status, new ArrayList<>());
}
// Lambda captures variable
String message = "Engine running.";
for (Engine engine : engines) {
if (!isRunning(engine)) {
logger.warn(() -> {
return String.format(message);
});
}
}
// Instance-bound method reference
for(Node node : nodes) {
descriptor = node.getDescription();
descriptor.ifPresent(dynamicTestExecutor::execute);
}
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
ObjectAllocationInLoop
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!
Was this page helpful?