Yep, checked all that. No leads yet.
Issue is there is no way to know when the memory jumps. Trace yields results which all look legit.
There is no way to know which ABAP stmt is causing the issue.
Shouldn't the memory be de-allocated at the end of a work process ?. Somehow this is not happening.