Hi Arend,

It is the working set memory associated with the process that is building up, not the private working set of the kix executable. Maybe someone with better understanding of how COM memory works could jump in here. The way I figure it is that the memory that is growing is the sole domain of the KiXforms dll and it is not releasing its resources as it should. I think the dll's memory is only unloaded once the parent process actually terminates. I believe this as the undelying dll remains file locked until the parent process exits.

Regards,

Richard