This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Poor Style: Explicit call to finalize()

From OWASP
Revision as of 14:47, 19 July 2006 by Weilin Zhong (talk | contribs)

Jump to: navigation, search
This article includes content generously donated to OWASP by MicroFocus Logo.png

This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.


Abstract

The finalize() method should only be called by the JVM after the object has been garbage collected.

Description

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.

Examples

The following code fragment calls finalize() explicitly:

	// time to clean up
	widget.finalize();

Related Threats

Related Attacks

Related Vulnerabilities

Related Countermeasures

Categories