Unfortunately I don't have time to check these "facts" for you, so this is only my guessing:
Message flow instances use memory from a shared pool allocated by the execution group. That's why it's difficult to know how much memory is getting consumed by an individual flow. The amount of memory consumed by a message flow varies heavily in function of time and is zero when the flow is not processing any messages. This means that all memory that is leaked by flow components will end up being owned by the execution group, not by the flow.
Execution group memory handling is optimized for high performance. The fact that execution groups don't release allocated memory is one indication of that.
If this contains false deduction, I hope somebody corrects me.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum