You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/20 16:23:01 UTC
DO NOT REPLY [Bug 31800] New: -
Memory Leak in Expirer.removeManagedObject (TimeStamp)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31800>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=31800
Memory Leak in Expirer.removeManagedObject (TimeStamp)
Summary: Memory Leak in Expirer.removeManagedObject (TimeStamp)
Product: Tomcat 3
Version: 3.3.2 Final
Platform: All
OS/Version: Other
Status: NEW
Severity: Critical
Priority: Other
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: david.blavier@one2team.com
The method Expirer.removeManagedObject (TimeStamp) leaks :
"managedObjs[managedCount-1] = null;" should be added here to prevent the leak.
public void removeManagedObject( TimeStamp ts ) {
for( int i=0; i< managedCount; i++ ) {
if( ts == managedObjs[i] ) {
synchronized( managedObjs ) {
managedObjs[ i ] = managedObjs[managedCount-1];
// should be added here to prevent a leak
managedObjs[managedCount-1] = null;
managedCount--;
}
return;
}
}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org