I had commented that .22 was pretty solid. It was up until a few days ago when it got all wound up on it self and all most seemed to hang the computer. It was still processing calls ok, but seemed real sluggish.
What I found was that it's memory footprint had grown quite large, something on the order of 250 meg of memory (as shown in task manager). It was still responsive so I tried to close it normally and it seemed like it would never close (I waited quite a while) so I forced it closed. As I recall while it was trying to close it was using 100 percent of 1 CPU.
Now I've had it running for about 4 days and the memory usage has continued to creep up. It is now at about 77 meg. I'm thinking that it will eventually get into the state I describe above. I'm not sure how long it had been running before, maybe 10 days.
I do notice that if I change the state of any of the windows (minimize/maximize) the memory foot print drops (at first to just 3-4 meg, then it jumps back up to near the original size.). Doing it just now it went from 77m to 65 m, in 5 minutes now it has gotten to 70 m.
I notice that the Call History has all the records from when it started, which I'm thinking is the issue, probably need to make that so it sheds older records in that list. I would think that having 1 days worth is more than enough.
I don't think this is new with .22 but I didn't recognize the cause/effect before when running earlier versions.
Thanks
DAK