Do not use StringBuffer or StringBuilder as a class field

Docs > コード分析 > Static Analysis Rules > Do not use StringBuffer or StringBuilder as a class field

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

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;
    }
    
}