Hi Magnus, thanks for having reported this. What you found is quite interesting and I will give a look at this issue asap. In the meanwhile it would be great if you could open a ticket about it here: https://issues.jboss.org/browse/DROOLS Thanks again and regards, Mario On Mon, Feb 11, 2013 at 10:56 AM, Magnus Vojbacke < magnus.vojbacke(a)digitalroute.com&gt; wrote: > Hi,**** > > ** ** > > I run into memory issues when using marshaling or unmarshalling Drools > stateful sessions.**** > > ** ** > > I was going to send this to rules-users, but I think the content is too > technical and implementation oriented to fit into that list.**** > > ** ** > > It seems that the memory consumption increases after a session has been > unmarshalled. That is to say: an unmarshalled session of size x uses much > more memory than if I had started with an empty session and inserted x > number of facts.**** > > ** ** > > Digging into a memory profile, I found that after unmarshalling, my > ReteooStatefulSession instance holds on to a MarshallerReaderContext > instance. The MarshallerReaderContext consumes a lot of memory.**** > > ** ** > > Digging into the unmarshalling code, it seems that the > MarshallerReaderContext is a utility class used during unmarshalling of > sessions. Intuitively, it seems wrong that a reference to this object > should be held after unmarshalling is finished.**** > > ** ** > > Is this a bug in Drools? Would it be ok if I filed this as an issue at > the Drools issue repository?**** > > _______________________________________________ > rules-dev mailing list > rules-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/rules-dev >

Hi, thank you for the quick reply Issue created: https://issues.jboss.org/browse/DROOLS-35 I included some code snippets from my marshalling/unmarshalling code. Hope this helps /Magnus -- View this message in context: http://drools.46999.n3.nabble.com/Memory-usage-MarshallerReaderContext-he... Sent from the Drools: Developer (committer) mailing list mailing list archive at Nabble.com. _______________________________________________ rules-dev mailing list rules-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev

Hi Mario, sorry for the delay! Attached is the reference chain between StatefulKnowledgeSessionImpl -> MarshallerReaderContext, according to the jvisualvm memory dump analysis feature. I extracted this information by looking at the "Closest GC root" path for the MarshallerReaderContext instance. StatefulKnowledgeSessionImpl : session ReteooStatefulSession : defaultEntryPoint NamedEntryPoint : objectStore SingleThreadedObjectStore : identityMap ObjectHashMap : table Entry[] : [0] ObjectHashMap$ObjectEntry : value DefaultFactHandle : lastLeftTuple RuleTerminalNodeLeftTuple : object AgendaItem : context PropagationContextImpl : readerContext MarshallerReaderContext : this -- View this message in context: http://drools.46999.n3.nabble.com/Memory-usage-MarshallerReaderContext-he... Sent from the Drools: Developer (committer) mailing list mailing list archive at Nabble.com. _______________________________________________ rules-dev mailing list rules-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-dev