Do not use StringBuffer or StringBuilder as a class field

문서 > Datadog 보안 > Code Security > Static Code Analysis (SAST) > SAST 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;
    }
    
}