We have a site coded in ASP.NET and see w3wp.exe crash every once in a
while. it also runs high on memory. Here is the IIS State log, If
someone here can determine what's happening in this log it would be
much appreciated.

Opened log file 'C:\iisstate\output\IISState-1700.log'

***********************
Starting new log output
IISState version 3.3.1

Wed Nov 30 10:26:21 2005

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 1700

Note: Thread times are formatted as HH:MM:SS.ms

***********************


IIS has crashed...
Beginning Analysis
DLL (!FunctionName) that failed: mscorwks!SafeRelease




Thread ID: 0
System Thread ID: 958
Kernel Time: 0:0:0.62
User Time: 0:0:0.265
Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
succeeded
Loaded Son of Strike data table version 5 from
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll"
Thread 0
ESP EIP


Begin System Thread Information

# ChildEBP RetAddr
00 0006fb24 79209074 mscorwks!SafeRelease+0x4d
01 0006fb40 792090a5 mscorwks!IUnkEntry::Free+0x7c
02 0006fb4c 7920915e mscorwks!ComPlusWrapper::ReleaseAllInterfaces+0xa
03 0006fd84 79208f61
mscorwks!ComPlusWrapper::ReleaseAllInterfacesCallBack+0x121
04 0006fd90 79208f92 mscorwks!ComPlusWrapper::Cleanup+0x16
05 0006fda0 79208faf
mscorwks!ComPlusContextCleanupGroup::CleanUpWrappers+0x19
06 0006fdac 7925a1be
mscorwks!ComPlusApartmentCleanupGroup::ReleaseCleanupGroup+0xe
07 0006fdd0 79207a0b
mscorwks!ComPlusApartmentCleanupGroup::CleanUpWrappers+0x7a
08 0006fe08 7921b6d9
mscorwks!ComPlusWrapperCleanupList::CleanUpWrappers+0x69
09 0006fecc 792159c1 mscorwks!ComPlusWrapperCache::ReleaseWrappers+0xf1
0a 0006fefc 79215960
mscorwks!ComPlusWrapperCache::ReleaseComPlusWrappers+0x28
0b 0006ff04 79215a8f mscorwks!CoEEShutDownCOM+0x24
0c 0006ff10 79179c0d mscorwks!CorExitProcess+0x38
0d 0006ff20 77bcaddb mscoree!CorExitProcess+0x46
0e 0006ff2c 77bcaefc msvcrt!__crtExitProcess+0x29
0f 0006ff5c 77bcaf52 msvcrt!_cinit+0xd3
10 0006ff70 01001a38 msvcrt!exit+0x11
11 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x140
12 0006fff0 00000000 kernel32!BaseProcessStart+0x23
Closing open log file C:\iisstate\output\IISState-1700.log
Opened log file 'C:\iisstate\output\IISState-1700.log'

Thanks,
John

What non-.NET COM component(s) are you using in your web pages?

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
We have a site coded in ASP.NET and see w3wp.exe crash every once in a
while. it also runs high on memory. Here is the IIS State log, If
someone here can determine what's happening in this log it would be
much appreciated.

Opened log file 'C:\iisstate\output\IISState-1700.log'

***********************
Starting new log output
IISState version 3.3.1

Wed Nov 30 10:26:21 2005

OS = Windows 2003 Server
Executable: w3wp.exe
PID = 1700

Note: Thread times are formatted as HH:MM:SS.ms

***********************


IIS has crashed...
Beginning Analysis
DLL (!FunctionName) that failed: mscorwks!SafeRelease




Thread ID: 0
System Thread ID: 958
Kernel Time: 0:0:0.62
User Time: 0:0:0.265
Thread Type: Managed Thread. Possible ASP.Net page or other .Net worker
succeeded
Loaded Son of Strike data table version 5 from
"C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll"
Thread 0
ESP EIP


Begin System Thread Information

# ChildEBP RetAddr
00 0006fb24 79209074 mscorwks!SafeRelease+0x4d
01 0006fb40 792090a5 mscorwks!IUnkEntry::Free+0x7c
02 0006fb4c 7920915e mscorwks!ComPlusWrapper::ReleaseAllInterfaces+0xa
03 0006fd84 79208f61
mscorwks!ComPlusWrapper::ReleaseAllInterfacesCallBack+0x121
04 0006fd90 79208f92 mscorwks!ComPlusWrapper::Cleanup+0x16
05 0006fda0 79208faf
mscorwks!ComPlusContextCleanupGroup::CleanUpWrappers+0x19
06 0006fdac 7925a1be
mscorwks!ComPlusApartmentCleanupGroup::ReleaseCleanupGroup+0xe
07 0006fdd0 79207a0b
mscorwks!ComPlusApartmentCleanupGroup::CleanUpWrappers+0x7a
08 0006fe08 7921b6d9
mscorwks!ComPlusWrapperCleanupList::CleanUpWrappers+0x69
09 0006fecc 792159c1 mscorwks!ComPlusWrapperCache::ReleaseWrappers+0xf1
0a 0006fefc 79215960
mscorwks!ComPlusWrapperCache::ReleaseComPlusWrappers+0x28
0b 0006ff04 79215a8f mscorwks!CoEEShutDownCOM+0x24
0c 0006ff10 79179c0d mscorwks!CorExitProcess+0x38
0d 0006ff20 77bcaddb mscoree!CorExitProcess+0x46
0e 0006ff2c 77bcaefc msvcrt!__crtExitProcess+0x29
0f 0006ff5c 77bcaf52 msvcrt!_cinit+0xd3
10 0006ff70 01001a38 msvcrt!exit+0x11
11 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x140
12 0006fff0 00000000 kernel32!BaseProcessStart+0x23
Closing open log file C:\iisstate\output\IISState-1700.log
Opened log file 'C:\iisstate\output\IISState-1700.log'

Thanks,
John

we are using a custom COM component. why?

Because it seems to be freeing some memory that it should not be... which
causes the crash later on.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
we are using a custom COM component. why?

ok, that's interesting. from looking at the w3wp.exe in Task Manager,
we see it consume a LOT of memory over time before it crashes. The
other day it was up to 876,000 K when we had to force the application
to recycle and reload the com objects.

Even if "w3wp.exe" is consuming memory it does not mean the issue has
anything to do with IIS. w3wp.exe is simply a host process that executes
user code... so 99% of the time it means that user code is doing something
to consume a LOT of memory.

http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx

I think that you are using some component that is mishandling memory by
either leaking or freeing it prematurely. Try running DebugDiag to help
diagnose what exactly is leaking memory, or Application Verifier -- both are
free tools from Microsoft to help troubleshoot common code issues.

The fact that w3wp.exe crashes does not mean that IIS is at fault; you have
to look at WHAT CODE is causing the crash since that is the code that is at
fault... and the tools I mentioned earlier help identify that code.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
[quoted text, click to view]
ok, that's interesting. from looking at the w3wp.exe in Task Manager,
we see it consume a LOT of memory over time before it crashes. The
other day it was up to 876,000 K when we had to force the application
to recycle and reload the com objects.