[jboss-jira] [JBoss JIRA] (DROOLS-498) Memory leak in stateful session after retracting facts

[Kent Anderson (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984425#comment-12984425 ] 

Kent Anderson edited comment on DROOLS-498 at 7/11/14 3:58 PM:
---------------------------------------------------------------

Screenshot (gcRoot.png) from Eclipse Memory Analysis showing shorted merged route to root.  MyEvent should be gone, since working memory is empty.


was (Author: kanderson.psware):
Screenshot from Eclipse Memory Analysis showing shorted merged route to root.  MyEvent should be gone, since working memory is empty.

> Memory leak in stateful session after retracting facts
> ------------------------------------------------------
>
>                 Key: DROOLS-498
>                 URL: https://issues.jboss.org/browse/DROOLS-498
>             Project: Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 6.0.1.Final
>            Reporter: Vitaly Lomov
>            Assignee: Mark Proctor
>            Priority: Minor
>         Attachments: gcRoot.png, memory-leak2.zip, screenshot1.png
>
>
> After adding many simple facts into the stateful session and then removing them, the factHandles for the removed facts are still referenced by the session. Eventually getting "java.lang.OutOfMemoryError: GC overhead limit exceeded" with the stack trace (sometimes) similar to DROOLS-411.
> Someone on StackOverflow suggested iterating through whatever factHandles remain after deletion and delete those, but I get no factHandles (correct, since I removed all facts).
> See screenshot for objects in memory _after_ deleting all facts.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)