The easy way would be to test the profiler against an application that will cause only one GC.
The simplest would be to create a HelloWorld program that calls Systsm.GC.Collect() once. This simple HelloWorld application will also guarantee that there is no MovedReferences callback is called--MovedReferences will add another level of complexity (we have to consider the old and new objectIDs). Display each allocation (objectID, classID) notified by the profiler (ObjectAllocated). Display each root reference (objectID, type) notified by RootReferences. Then, we will notice that there will be some lines/objectIDs (excluding NULL) whose allocation is not notified by ObjectAllocated. Memomana =================================== This list is hosted by DevelopMentorŪ http://www.develop.com ASP.NET courses you may be interested in: Guerrilla ASP.NET 15 March 2004, in Boston, MA 17 May 2004 in Torrance, CA 7 June 2004, London, UK http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
