|
|
Status: Draft Weakness ID: 586 (Weakness Variant)Description Summary The software makes an explicit call to the finalize() method from outside the finalizer. Potential Mitigations Do not make explicit calls to finalize(). Use static analysis tools to spot such instances. Demonstrative Examples The following code fragment calls finalize() explicitly: // time to clean up widget.finalize();
Other Notes While the Java Language Specification allows an object's finalize() method to be called from outside the finalizer, doing so is usually a bad idea. For example, calling finalize() explicitly means that finalize() will be called more than once: the first time will be the explicit call and the last time will be the call that is made after the object is garbage collected. Relationships
Applicable Platforms Languages Java Time of Introduction  ImplementationContent History Modifications Eric Dalci. Cigital. 2008-07-01. (External) updated Name, Potential_Mitigations, Time_of_Introduction CWE Content Team. MITRE. 2008-09-08. (Internal) updated Relationships, Other_Notes Previous Entry Names Explicit Call to Finalize (changed 2008-09-09) |
|
|
|||
