Possible memory leak insliding temporal windows ------------------------------------------------ Key: DROOLS-263 URL: https://issues.jboss.org/browse/DROOLS-263 Project: Drools Issue Type: Bug Affects Versions: 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Blocker When an event is asserted and a temporal window is present, it will be cached in the window's memory and then propagated (usually to an accumulate) by a propagationQuquingNode. If the even expires before it participates in a tuple (in a multi-threading environment), the WM retraction will not reach the window node due to the lack of tuples. BUT, it will set the fact handle's ID to -1 When the fact is considered for expiration from the sliding window, its changed ID will 1) disrupt the local event queue and 2) prevent it from being removed from the node memory. Memory leaks and NPEs will arise randomly