[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-557) Memory leak when using default ReaderProvider with Master/Slave Directories

[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-557?pag... ] Sanne Grinovero commented on HSEARCH-557: ----------------------------------------- Hi, without reusing the same Directory instance you're introducing a memory leak: the default ReaderProvider is tracking open indexes using the Directory as a key, and for each Directory instance it will keep at least a single IndexReader open. So in the HS implementation you'll have a minimum of 2 IndexReaders open (when all clients have closed all), but because you're closing Directories and opening new ones you're experiencing an unbounded number of open readers (each of which is caching the fields..). This might explain why I'm not reproducing this; could you please check the behaviour on Hibernate Search 3.2 reverting your changes on the DirectoryProvider? -- 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira