[ https://issues.jboss.org/browse/DROOLS-1233?page=com.atlassian.jira.plugi... ] Jon Kranes updated DROOLS-1233: ------------------------------- Steps to Reproduce: Run the attached unit test in debug mode with a breakpoint at System.out line specified. While the program is paused take a heap dump using jvisualvm after performing a GC. The heap dump will show instances of TestClass remain in memory even though they have been removed from the session. The attached screen shots show the jvisualvm class view and the reference path from an instance of TestClass to the drools Session. Note that the heap dump shows that Drools is holding 200,000 instances of DefaultFactHandle, which includes the 100,000 expected instances corresponding to 100,000 instances of TestClass2, but also an additional 100,000 instances corresponding to the removed facts for instances of TestClass. These additional 100,000 DefaultFactHandle instances in memory are not available through the KieSession API and thus cannot be programmatically removed in any obvious way. (was: Run the attached unit test in debug mode with a breakpoint at System.out line specified. While the program is paused take a heap dump using jvisualvm after performing a GC. The heap dump will show instances of TestClass remain in memory even though they have been removed from the session. The attached screen shots show the jvisualvm class view and the reference path from an instance of TestClass to the drools Session.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)