Hello,

I am experiencing a problem with an MDI app that I have written in Visual
Basic.Net using the 1.1 version of the Framework. The application "leaks"
memory. It appears that, over time, as more and more forms are opened and
closed, references to some object are not getting cleaned up in the app
(these resources are released when the app is closed, however). When I run
the "CLR Memory - Bytes in All Heaps" performance counter in the Performance
Monitor, garbage collections can be seen, but over a long period of time the
heap size grows without bound.

In order to show this behavior, I put a timer in my MDI application that
simply opens and closes a form every few seconds. Then I would start this
test app on various machines and monitor it over about a 12-hour period. The
strange thing about the results, however, is that they seem to show
different behaviors between Windows XP and Windows 2000 machines. When the
test is run on a Windows 2000 machine, the CLR heap size seems to stay
constant. When it runs on an XP machine, the CLR grows without bounds.

So I guess my questions are as follows...
Does anyone have any suggestions as to what might be causing this? What kind
of things should I be looking for in my app that would cause this? Is there
any reason that the app would be behaving differently under the two
different operating systems?  Has anyone had a similar problem, and if so,
what is the best way to debug a "resource leak" like this?

Any help would be greatly appreciated.

Thank you,
David Miller