Also, here's a blog discussing available tools for memory management:

http://blogs.msdn.com/ce_base/archive/2006/01/11/511883.aspx


>Hi there, all,
>
>Boy, it's been a while since I've been on here. Well, didn't need to for the longest. I working for the state for a long time and didn't have much to do :-) (hey, sorry to all state workers, but it's the truth).
>
>Anyway, I have a new job now and I have an issue that's giving me grief and I hope you can help me with. I inherited an embedded application that's steadily growing in program memory usage. We're developming in Visual Studio 2003 for a Windows CE.net platform and using Visual Basic. The program memory is increasing but I was under the impression that all local variables are marked available for garbage collection once the routine in which they're declared is finished. I'm figuring I've got something out there that is not being released but other than going through several routines (and I mean a lot), I can't find another way to find what's happening.
>
>Could someone give me some ideas of any time-effective solutions for finding the increasing memory? I'd greatly appreciate it.