Do not use StringBuffer or StringBuilder as a class field

Documentos > Code Analysis > Static Analysis Rules > Do not use StringBuffer or StringBuilder as a class field

This page is not yet available in Spanish. We are working on its translation.
If you have any questions or feedback about our current translation project, feel free to reach out to us!

Metadata

ID: java-best-practices/string-buffer-field

Language: Java

Severity: Warning

Category: Best Practices

Description

StringBuffers and StringBuilders have the potential to grow significantly, which could lead to memory leaks if they are retained within objects with extended lifetimes.

Non-Compliant Code Examples

public class Foo {
    
    private StringBuffer buffer1;    // potential memory leak as an instance variable;
    private String buffer2;
    private StringBuilder buffer3;    // potential memory leak as an instance variable;

}

Compliant Code Examples

public class Foo {
    
    public void method() {
        StringBuffer buffer;
    }
    
}