Difference between revisions of "Code Correctness: Call to System.gc()"
| Line 3: | Line 3: | ||
__TOC__ | __TOC__ | ||
| + | |||
| + | [[ASDR Table of Contents]] | ||
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}''' | ||
| − | |||
| − | |||
| − | |||
==Description== | ==Description== | ||
| Line 91: | Line 90: | ||
[[Category:API Abuse]] | [[Category:API Abuse]] | ||
[[Category:OWASP ASDR Project]] | [[Category:OWASP ASDR Project]] | ||
| + | [[Category:Vulnerability]] | ||
Revision as of 11:52, 29 October 2008
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Contents
Last revision (mm/dd/yy): 10/29/2008
Description
Explicit requests for garbage collection are a bellwether indicating likely performance problems.
At some point in every Java developer's career, a problem surfaces that appears to be so mysterious, impenetrable, and impervious to debugging that there seems to be no alternative but to blame the garbage collector. Especially when the bug is related to time and state, there may be a hint of empirical evidence to support this theory: inserting a call to System.gc() sometimes seems to make the problem go away.
In almost every case we have seen, calling System.gc() is the wrong thing to do. In fact, calling System.gc() can cause performance problems if it is invoked too often.
Risk Factors
TBD
Examples
TBD
Related Attacks
Related Vulnerabilities
Related Controls
Related Technical Impacts
References
Note: A reference to related CWE or CAPEC article should be added when exists. Eg:
