[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-310) Out of Memory on ScrollableResults
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310?pag...
]
Sanne Grinovero commented on HSEARCH-310:
-----------------------------------------
As I've written on the hibernate-dev list; I think the entities should be evicted
from the persistence context to really solve the memory leak.
It is quite tricky to detect when to evict them.
Out of Memory on ScrollableResults
----------------------------------
Key: HSEARCH-310
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310
Project: Hibernate Search
Issue Type: Bug
Components: query
Affects Versions: 3.0.1.GA
Environment: Java SE, 3.0.1.GA
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 3.1.1
http://forum.hibernate.org/viewtopic.php?p=2400452
I think this is more appropriate for 3.1.1
Emmanuel said:
"The implementation suffers several flows:
- we do create an EntityInfo[] as big as the number of hits
- we lazily load this array but we never release "old content"
- we lazily load the content (ie objects) by window but we never release it
Some Soft reference based cache can help."
--
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