professerspatula,

I agree with much of that.

The other aspect that CA should be paying attention to is that adding memory merely masks the problem. The problem is still there and indicates errors in the base code that are accumulating. If it started with lag, and stayed the same, then I wouldn't be calling it a leak. It is the progressive nature of the problem that points to application flaws.

(If I had to shut down Excel every few hours because it got progressively slower, then I would know there was a problem with Excel. Ditto for IE, word, or any other app.)