Memory leak in FileCacheLoader
------------------------------
Key: JBCACHE-96
URL: http://jira.jboss.com/jira/browse/JBCACHE-96
Project: JBoss Cache
Type: Bug
Reporter: Bela Ban
Assigned to: Bela Ban
Fix For: 1.2.1
Attachments: FileCacheLoader.java
There is a memory leak probably caused by a growing HashMap in FileCacheLoader
(and possibly other loaders). Please refer to the attached file, fetched from
cvs head as of February 21. The memory leaked is proportional to the number of
objects put into the cache and their sizes. This is true for the cache version
1.1.1 and 1.2 when run inside JBoss 3.2.1, I haven't had the time to test it on
version 4.
The problem seems to be that the HashMap does not get cleaned up when
committing a transaction. The cleanup only happens on rollback in the standard
code.
With the modification in line 198 the leak is sealed, but please note that I
have no experience with the JBoss-cache source whatsoever, and no tests have
been made apart from determining that the leak is gone. Tests have only been
made with the cache configured to be local.
Best regards
Tom Bakken
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development