from the perfmon output of a simple esdtoaod job in 16.6.3.2:

py:perfmonsvc        info naive vmem-leak estimation: (nevts=1622)
py:perfmonsvc        info   first-evt vmem:   728.395 mb
py:perfmonsvc        info   10th -evt vmem:   728.395 mb
py:perfmonsvc        info   last -evt vmem:   901.172 mb
py:perfmonsvc        info   slope[10:-1]:     109.078 kb/evt

this job didn't do monitoring, that why the numbers are so low to start with.

i ran valgrind on a short job, but nothing came up. so, it's not a real leak, someone's filling a vector, but doesn't clear it at the end of an event. something like this. thomas, could it be the new perfmon suite ? 

cheers, rolf
