Reported on Zulip:

Rama

While running the example from https://github.com/kiegroup/kogito-examples/tree/stable/kogito-quarkus-examples/process-business-rules-quarkus. I observed that the mutiple kie sessions are created under ruleunit and are not getting released even during GC. Looks like it is a bug in the Rule unit session creation . Sessions are not getting disposed. As in the attached profile from Jprofiler, the Kiesessions are held under the ruleunit and are not released , please refer https://kie.zulipchat.com/#narrow/stream/232676-kogito/topic/bpmn.20process.20drl.20memory.20leak

Ranjan Das

Hi team

Facing an issue of memory leakage with kogito quarkus application , drl file when called from a bpmn process as a rule-unit, the amount of memory it is consuming during the rule load and execution is not able to release the memory from the
heap even after garbage collector has run.And the problem is by hitting the server with more request this memory consumption is increasing and ultimately the server/pod is going out of memory

But when the same drl file is run as a individual rule unit it is able to release the memory.
The above operation is performed using a 5mb payload and 10 rules in a single drl file with a bpmn process calling the drl as a ruleunit from the rule task of the process.

...

Actually its not in my personal laptop i will have to recreate it in my personal laptop and then will be able to share .
But i think that this is not a project secific scenario. if u create a small bpmn process with one ruletask calling a single drl as a rule unit and then try to do a performance testing through jmeter and watch the heap memory .. U will be able to observer it.

—