Poor Style: Explicit call to finalize()

From OWASP
Jump to: navigation, search


This page was marked to be reviewed for deletion.


#REDIRECT Failure to follow guideline/specification


Last revision (mm/dd/yy): 04/7/2009


Contents

Description

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

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.


Risk Factors

TBD

Examples

The following code fragment calls finalize() explicitly:

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

Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

TBD