Poor Style: Explicit call to finalize() - Revision history

KirstenS at 23:27, 7 April 2009

2009-04-07T23:27:11Z

KirstenS at 16:27, 17 February 2009

2009-02-17T16:27:09Z

KirstenS at 15:26, 5 November 2008

2008-11-05T15:26:09Z

KirstenS at 12:45, 30 September 2008

2008-09-30T12:45:30Z

Weilin Zhong at 16:44, 19 July 2006

2006-07-19T16:44:36Z

Weilin Zhong at 14:47, 19 July 2006

2006-07-19T14:47:46Z

Weilin Zhong at 18:50, 18 July 2006

2006-07-18T18:50:33Z

Weilin Zhong at 18:12, 18 July 2006

2006-07-18T18:12:29Z

Weilin Zhong at 15:05, 18 July 2006

2006-07-18T15:05:41Z

New page

{{Template:Fortify}}

{{Template:Vulnerability}}

==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:

<pre>
// time to clean up
widget.finalize();

</pre>

==Related Threats==

==Related Attacks==

==Related Vulnerabilities==

==Related Countermeasures==

==Categories==

{{Template:Stub}}

[[Category:API Abuse]]

[[Category:Java]]

[[Category:Implementation]]

[[Category:Code Snippet]]

← Older revision		Revision as of 23:27, 7 April 2009
Line 3:		Line 3:
	#REDIRECT [[Failure to follow guideline/specification]]		#REDIRECT [[Failure to follow guideline/specification]]

−	~~__TOC__~~
−
−	~~[[ASDR Table of Contents]]~~

@@ Line 1: / Line 1: @@
-{{Template:Vulnerability}}
+{{template:CandidateForDeletion}}
-{{Template:Fortify}}
 __TOC__
@@ Line 8: / Line 9: @@
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
@@ Line 59: / Line 58: @@
 TBD

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
+__TOC__
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
-[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
@@ Line 95: / Line 95: @@
 [[Category:Implementation]]
 [[Category:Code Snippet]]

← Older revision		Revision as of 16:44, 19 July 2006
Line 1:		Line 1:
		+	{{Template:Vulnerability}}
	{{Template:Fortify}}		{{Template:Fortify}}
−	~~{{Template:Vulnerability}}~~

	==Abstract==		==Abstract==

← Older revision		Revision as of 14:47, 19 July 2006
Line 1:		Line 1:
	{{Template:Fortify}}		{{Template:Fortify}}
−
	{{Template:Vulnerability}}		{{Template:Vulnerability}}

@@ Line 2: / Line 2: @@
 {{Template:Fortify}}
-==Abstract==
+[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 ==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:
@@ Line 20: / Line 33: @@
 </pre>
-==Related Threats==
+==Related [[Attacks]]==
-==Related Attacks==
+Session Management Vulnerability]]
-==Related Vulnerabilities==
+__NOTOC__
-==Categories==
+[[Category:OWASP ASDR Project]]
 [[Category:Use of Dangerous API]]
 [[Category:API Abuse]]