https://wiki.owasp.org/api.php?action=feedcontributions&feedformat=atom&user=Swapnild 2026-04-23T13:25:45Z User contributions MediaWiki 1.27.2 https://wiki.owasp.org/index.php?title=Code_Correctness:_Call_to_System.gc()&diff=23911 2007-12-07T10:29:26Z

<p>Swapnild: /* Examples */</p> <hr /> <div>{{Template:Vulnerability}}<br /> {{Template:Fortify}}<br /> <br /> ==Abstract==<br /> <br /> Explicit requests for garbage collection are a bellwether indicating likely performance problems.<br /> <br /> ==Description==<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> <br /> <br /> ==Related Threats==<br /> <br /> ==Related Attacks==<br /> <br /> ==Related Vulnerabilities==<br /> <br /> ==Related Countermeasures==<br /> <br /> ==Categories==<br /> <br /> [[Category:Use of Dangerous API]]<br /> <br /> [[Category:Java]]<br /> <br /> [[Category:Implementation]]<br /> <br /> [[Category:API Abuse]]</div>

Swapnild https://wiki.owasp.org/index.php?title=Code_Correctness:_Call_to_System.gc()&diff=23910 2007-12-07T10:29:08Z

<p>Swapnild: /* Examples */</p> <hr /> <div>{{Template:Vulnerability}}<br /> {{Template:Fortify}}<br /> <br /> ==Abstract==<br /> <br /> Explicit requests for garbage collection are a bellwether indicating likely performance problems.<br /> <br /> ==Description==<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> ==Examples ==<br /> ghrht<br /> <br /> ==Related Threats==<br /> <br /> ==Related Attacks==<br /> <br /> ==Related Vulnerabilities==<br /> <br /> ==Related Countermeasures==<br /> <br /> ==Categories==<br /> <br /> [[Category:Use of Dangerous API]]<br /> <br /> [[Category:Java]]<br /> <br /> [[Category:Implementation]]<br /> <br /> [[Category:API Abuse]]</div>

Swapnild