Memory leak in WMS response handling
------------------------------------
Key: GEOS-1668
URL: http://jira.codehaus.org/browse/GEOS-1668
Project: GeoServer
Issue Type: Bug
Components: WMS
Affects Versions: 1.6.0-RC2
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 1.6.0, 1.7.0-beta1
DefaultMapContext attaches listeners to the feature source, these listeners are referenced by FeatureListenerManager and are never cleaned up, meaning each request builds up a new featuresource/defaultmapcontext couple in featureListenerManager. The leak is usually small, but can become sizeable if the styles used by the map context are big.
We should clean up after ourselves when the response is done (the cleanup code there, but for some strange reason it has been commented out when merging the WCS branch one year ago), but at the same time FeatureListenerManager should be smarter and use weak references to avoid this kind of issues
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira