[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-310) Out of Memory on ScrollableResults

[Emmanuel Bernard (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33086#action_33086 ] 

Emmanuel Bernard commented on HSEARCH-310:
------------------------------------------

I've reviewed the code, Looks good except that we are still creating an array of the size of the number of hits (LoadedObject[] in this case)
We no longer leak but we might take a "certain fixed amount of memory" :)

looks good to me as a commit, we can get back to it down the road when we are bored.

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira