Try reading " Code Complete, Second Edition", it gives good info on design patterns, and reasons for memory leaks. Yes, with every new version of .NET framework, GC is modified and many issues are fixed with the older version.
On Mar 13, 1:47 am, mredmond <[email protected]> wrote: > Hi Folks, > > We've got a number of .NET 1.1 applications that are having horrible > memory leakage issues. Similar applications running under 2.0 do not > have nearly as many problems. On the servers having the issues, > Perfmon shows the Gen02 GC heap slowly ratcheting up until the > application fails. > > We are in the process of band-aiding the problems using app pools and > auto-restarts of the app pools when memory thresholds are reached. > This isn't a long-term solution but we're hopeful it will get the job > done for the time being. In the short-term, fixing or rewriting the > apps isn't an option, nor is porting to 2.0. > > My primary concern right now is to identify why this issue is > happening and what coding practices might prevent it in the future. > > Can anyone explain to me the differences between garbage collection in > framework versions 1.1 and 2.0? > > Is is possible that the GC in version 1.1 doesn't do a good job of > cleaning up unmanaged resources? One thing I've noticed is that our > developers *never* call the Dispose() method on objects. > > Thanks!
