I forgot to include info about the environment the program and CLR Profiler are being used:
The app was developed using C# (no unsafe features). It uses/allocates about 180-220mb when it runs. Outside of CLR Profiler, it runs to completion with no errors. It also runs to completion with the DevPartner profiler product. The issues arise with CLR Profiler v1.1 - the version touted as V2 on it's MS download site Environment: - .NET v1 (app built with VS2002) - Windows XP SP1 The finished app will [mostly] run on: - .NET v1 (and .NET v1.1+ in some cases) - Windows 2000 Server & Windows 2003 server (and XP to a lesser extent) Cheers, Kunle > The CLR Profiler tool always crashes part-way through when I > use it to profile an app I'm developing. Outside of CLR > Profiler, the app normally runs for about 20 minutes doing > heavy text processing. With CLR Profiler it runs for about > 2-5 minutes and then triggers an assert dialog in the > underlying Visual C++ debug library. > > The relevant info from the assert dialog is: > > Message: Debug Assertion Failed! > File: dbgheap.c > Line: 346 > Expression: _CrtCheckMemory() > > Does anyone here know what this might mean? > > Kunle > > =================================== > This list is hosted by DevelopMentorR http://www.develop.com > Some .NET courses you may be interested in: > > NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles > http://www.develop.com/courses/gaspdotnetls > > View archives > and manage your subscription(s) at http://discuss.develop.com > =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
