I'm trying to use the CLRProfiler to profile an ASP.Net application. Somehow, it's gotten into a state where it crashes aspnet_wp. Running the same app without profiling works fine. The event log entries when it crashes are:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 12/7/2006
Time: 12:46:25 PM
User: N/A
Computer: AFORS1
Description:
Faulting application aspnet_wp.exe, version 2.0.50727.210, stamp 45063b16, faulting module profilerobj.dll, version 0.0.0.0, stamp 436a3905, debug 0, fault address 0x00006860.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:.. [clipped]
Followed by:
Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1000
Date: 12/7/2006
Time: 12:46:38 PM
User: N/A
Computer: AFORS1
Description:
aspnet_wp.exe (PID: 3084) stopped unexpectedly.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
The version of CLRProfiler I'm using is:
| File Name: | CLRProfiler.EXE |
| Version: | 1.0 |
| Date Published: | 12/7/2005 |
| Language: | English |
| Download Size: | 4.9 MB |
Has anyone else seen this The profiler works fine for other applications. I've changed my setup to run as SYSTEM, as recommended in the FAQ section of the doc, but that made no difference. None of the other troubleshooting tips in the FAQ have helped either.
While I may have something odd in my app that contributes to this, I would consider it a bug that the profiler is able to crash asp.net in this way.
CLRProfiler crashes aspnet_wp
JSR2005
Quick update. Many readers contacted my blog for an updated CLR Profiler and reported that their problem disappeared after using the updated version. We have now posted the updated version officially here:
http://www.microsoft.com/downloads/details.aspx FamilyID=a362781c-3870-43be-8926-862b40aa0cd0&DisplayLang=en
So please feel free to go there directly to get the latest and greatest. (The update is for CLR 2.x only).
Thanks all for your help!
Chris Gin
I wonder if you might be in a state where the wrong version of the CLR Profiler DLL (ProfilerObj.dll) is getting loaded. Looks like your asp.net is using CLR 2.x, so you'll want CLR Profiler 2.0. You might try reinstalling CLR Profiler 2.0 to make sure the right ProfilerObj.dll is registered, and then rebooting.
http://www.microsoft.com/downloads/details.aspx FamilyID=a362781c-3870-43be-8926-862b40aa0cd0&DisplayLang=en
nightowl4642002
Hi, Alan, sorry you're still having trouble. I spoke with the owner of CLR Profiler, and he did mention that there was a bug where the profiler DLL could sometimes crash when threads were created or destroyed (he didn't remember for sure which).
Would you like me to send you a pre-release, as-is, no-warranties-intended-or-implied copy of the profiler that should fix the bug he was thinking of If it fixes your problem as well, great, and if not, perhaps we could look at a dump and try to get to the bottom of this.
If you send me your email address, I can e-mail you the zip file containing the updated profiler. If you'd rather not publicize your email address in a public forum, you can privately send it to me via my blog: http://blogs.msdn.com/davbr/contact.aspx.
Muhsin Zahid Uğur