[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-557) Memory leak when using default ReaderProvider with Master/Slave Directories
Sanne Grinovero (JIRA)
noreply at atlassian.com
Sat Jul 17 04:26:14 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero updated HSEARCH-557:
------------------------------------
Assignee: Sanne Grinovero
Affects Version/s: (was: 3.2.0.Final)
(was: 3.1.1.GA)
Fix Version/s: (was: 3.3.0)
removing assignement from versions as it didn't appear to affect them.
> Memory leak when using default ReaderProvider with Master/Slave Directories
> ---------------------------------------------------------------------------
>
> Key: HSEARCH-557
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-557
> Project: Hibernate Search
> Issue Type: Bug
> Components: directory provider
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
>
> The default ReaderProvider, org.hibernate.search.reader.SharingBufferReaderProvider is keeping a reference to an open index of the most current IndexReader, so it's able to refresh this on demand and track references to previously opened instances.
> The currently open indexReaders for the not-active directory might consume a lot of memory; follows a forum reference where it appears to be a memory leak; still not sure if it's a leak or just needing twice as much memory as otherwise, please comment here.
> https://forum.hibernate.org/viewtopic.php?f=9&t=1005540
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list