[jboss-jira] [JBoss JIRA] (DROOLS-498) Memory leak in stateful session after retracting facts
[
https://issues.jboss.org/browse/DROOLS-498?page=com.atlassian.jira.plugin...
]
Kent Anderson commented on DROOLS-498:
--------------------------------------
Adding the above-mentioned forceGcUnlinkedRules() call after the final fireAllRules() call
does not remove the StockTick object from the internal memory, even after factCount
returns to 0. Is there some other trick to getting this to work?
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: Mario Fusco
Priority: Critical
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)