Welcome to MobyThreads.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in
All support for the MobyThreads Threaded phpBB MOD can now be found on welsolutions at this forum

DLLHOST High Mem Usage

 
   Web Hosting and Web Master Forums (Home) -> IIS RSS
Next:  Deny Read access for asp file is ignored by iis  
Author Message
teiszler

External


Since: Nov 15, 2004
Posts: 4



(Msg. 1) Posted: Mon Nov 15, 2004 10:15 am
Post subject: DLLHOST High Mem Usage
Archived from groups: microsoft>public>inetserver>iis (more info?)

Throughout the course of writing a php page that calls a COM dll I
experienced errors that I believe were related to some sort of memory leak.
Now when I simply goto my localhost (without even going to the php page that
loads the COM object), the dllhost process immediately commits over 200MB of
memory. I am running Win2k SP4. Any help is greatly appreciated.

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

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

Mon Nov 15 10:02:04 2004

OS = Windows 2000
Executable: dllhost.exe
PID = 2308

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

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




Thread ID: 0
System Thread ID: 8e8
Kernel Time: 0:0:0.15
User Time: 0:0:0.15
Thread Type: Other
# ChildEBP RetAddr
00 0006fd28 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
01 0006fd50 7c57b3db KERNEL32!WaitForSingleObjectEx+0x71
02 0006fd60 77aaa701 KERNEL32!WaitForSingleObject+0xf
03 0006fd80 77aa9f0f
ole32!CSurrogateProcessActivator::WaitForSurrogateTimeout+0x4f
04 0006fd9c 01001230 ole32!CoRegisterSurrogateEx+0x169
05 0006ff24 010014c6 dllhost!WinMain+0xb0
06 0006ffc0 7c59893d dllhost!WinMainCRTStartup+0x156
07 0006fff0 00000000 KERNEL32!BaseProcessStart+0x3d




Thread ID: 1
System Thread ID: 864
Kernel Time: 0:0:5.468
User Time: 0:0:1.125
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made

# ChildEBP RetAddr
00 00d9fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
01 00d9ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
02 00d9ff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
03 00d9ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
04 00d9ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
05 00d9ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 2
System Thread ID: a9c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00ddff5c 7c59a243 ntdll!NtDelayExecution+0xb
01 00ddff7c 7c59a20e KERNEL32!SleepEx+0x32
02 00ddff88 77ab8ffb KERNEL32!Sleep+0xb
03 00ddff90 77ab50ee ole32!CROIDTable::WorkerThreadLoop+0xc
04 00ddffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x22
05 00ddffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
06 00ddffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 3
System Thread ID: 8e4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 00e1ff30 77abbad5 USER32!NtUserGetMessage+0xb
01 00e1ff70 77abba23 ole32!CDllHost::STAWorkerLoop+0x40
02 00e1ff8c 77abb95e ole32!CDllHost::WorkerThread+0xc2
03 00e1ff90 77ab50ee ole32!DLLHostThreadEntry+0x9
04 00e1ffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x22
05 00e1ffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
06 00e1ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 4
System Thread ID: a7c
Kernel Time: 0:0:0.46
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0125fc54 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
01 0125fc80 6de8b9d0 KERNEL32!GetQueuedCompletionStatus+0x27
02 0125fd94 6de8b908 TxfAux!WORK_QUEUE::WorkerLoop+0xa0
03 0125ffb4 7c57b388 TxfAux!WORK_QUEUE::ThreadLoop+0x58
04 0125ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 5
System Thread ID: a1c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 01f5ff08 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
01 01f5ff58 7c59a0c2 KERNEL32!WaitForMultipleObjectsEx+0xea
02 01f5ff70 787f58ce KERNEL32!WaitForMultipleObjects+0x17
03 01f5ffb4 7c57b388 COMSVCS!CEventDispatcher::PushEvents+0x4e
04 01f5ffc0 01e3efe0 KERNEL32!BaseThreadStart+0x52
WARNING: Frame IP not in any known module. Following frames may be wrong.
05 017288f0 01ee6000 0x1e3efe0
06 017288f0 01ee6000 0x1ee6000
07 017276d0 01ee4000 0x1ee6000
08 017287b0 01ee2000 0x1ee4000
09 01728530 01f0e000 0x1ee2000
0a 01727f18 01f0c000 0x1f0e000
0b 01728e18 01f0a000 0x1f0c000
0c 01727e28 01f08000 0x1f0a000
0d 01728a58 01f02000 0x1f08000
0e 013f7b88 01f00000 0x1f02000
0f 01727ea0 01efc000 0x1f00000
10 017274c8 01e90000 0x1efc000
11 017286e8 0186a000 0x1e90000
12 01727d60 01714000 0x186a000
13 013f7c00 01744000 0x1714000
14 00074028 00cbe000 0x1744000
15 017282b0 01e8e000 0xcbe000
16 01727068 01884000 0x1e8e000
17 01728e40 01882000 0x1884000
18 01727e50 0187e000 0x1882000
19 01728ff8 0187c000 0x187e000
1a 017270b8 01878000 0x187c000
1b 017287d8 01876000 0x1878000
1c 017262f8 01870000 0x1876000
1d 01728120 0186e000 0x1870000
1e 01728e90 01830000 0x186e000
1f 01727158 0182e000 0x1830000
20 01726eb0 0171e000 0x182e000
21 01728d50 01eda000 0x171e000
22 01728670 01ebe000 0x1eda000
23 017271f8 01eba000 0x1ebe000
24 01726ed8 01ea0000 0x1eba000
25 01726820 0172a000 0x1ea0000
26 017271a8 016f6000 0x172a000
27 013f7930 016e4000 0x16f6000
28 01728f30 01efe000 0x16e4000
29 01727e78 01efa000 0x1efe000
2a 01727e00 01ef8000 0x1efa000
2b 017260c8 01ea2000 0x1ef8000
2c 01729098 01e9e000 0x1ea2000
2d 01729070 01e9c000 0x1e9e000
2e 01728f58 01824000 0x1e9c000
2f 01728cd8 01820000 0x1824000
30 01729048 01e92000 0x1820000
31 01727ec8 01e8c000 0x1e92000




Thread ID: 6
System Thread ID: 9b4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

Remote call is either to a MTA object or object not initialized. Also,
possible utility thread.
DCOM call being made to Process ID: 2220
Waiting on thread id: ffffffff

# ChildEBP RetAddr
00 01f9fb68 77d4256d ntdll!ZwRequestWaitReplyPort+0xb
01 01f9fb94 77d3ac56 RPCRT4!LRPC_CCALL::SendReceive+0x11e
02 01f9fba0 77b25b87 RPCRT4!I_RpcSendReceive+0x2c
03 01f9fbc0 77b25a52 ole32!ThreadSendReceive+0xef
04 01f9fbd8 77b22ab6 ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x14f
05 01f9fc18 77b258c6 ole32!CRpcChannelBuffer::SendReceive2+0x96
06 01f9fc28 77a6cb5d ole32!CRpcChannelBuffer::SendReceive+0x11
07 01f9fc88 77ab74c3 ole32!CAptRpcChnl::SendReceive+0xa9
08 01f9fce0 77d94c1a ole32!CCtxComChnl::SendReceive+0x124
09 01f9fcfc 77d9487d RPCRT4!NdrProxySendReceive+0x4c
0a 01f9ff44 77d95136 RPCRT4!NdrClientCall2+0x4f5
0b 01f9ff60 77d46e75 RPCRT4!ObjectStublessClient+0x76
0c 01f9ff70 787f5818 RPCRT4!ObjectStubless+0xf
0d 01f9ffb4 7c57b388
COMSVCS!CEventDispatcher::GetEventServerInfoThread+0x118
0e 01f9ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 7
System Thread ID: 300
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 01fdfee0 7c59a243 ntdll!NtDelayExecution+0xb
01 01fdff00 7c59a20e KERNEL32!SleepEx+0x32
02 01fdff0c 787d12aa KERNEL32!Sleep+0xb
03 01fdff7c 780085bc COMSVCS!PostData+0xf2
04 01fdffb4 7c57b388 MSVCRT!_endthreadex+0xc1
05 01fdffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 8
System Thread ID: a40
Kernel Time: 0:0:1.140
User Time: 0:0:0.765
Thread Type: Other
# ChildEBP RetAddr
00 02a6fe5c 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
01 02a6feac 77e119e6 KERNEL32!WaitForMultipleObjectsEx+0xea
02 02a6ff08 77e11ace USER32!MsgWaitForMultipleObjectsEx+0x153
03 02a6ff24 6e5a5a7c USER32!MsgWaitForMultipleObjects+0x1d
04 02a6ff7c 780085bc IISRTL!SchedulerWorkerThread+0xa7
05 02a6ffb4 7c57b388 MSVCRT!_endthreadex+0xc1
06 02a6ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 9
System Thread ID: 894
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 02aafe5c 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
01 02aafeac 77e119e6 KERNEL32!WaitForMultipleObjectsEx+0xea
02 02aaff08 77e11ace USER32!MsgWaitForMultipleObjectsEx+0x153
03 02aaff24 6e5a5a7c USER32!MsgWaitForMultipleObjects+0x1d
04 02aaff7c 780085bc IISRTL!SchedulerWorkerThread+0xa7
05 02aaffb4 7c57b388 MSVCRT!_endthreadex+0xc1
06 02aaffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 10
System Thread ID: 6b4
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 02d6ff50 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
01 02d6ff7c 6d702957 KERNEL32!GetQueuedCompletionStatus+0x27
02 02d6ffb4 7c57b388 ISATQ!AtqPoolThread+0x40
03 02d6ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 11
System Thread ID: 8b8
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: HTTP Listener
# ChildEBP RetAddr
00 02daff50 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
01 02daff7c 6d702957 KERNEL32!GetQueuedCompletionStatus+0x27
02 02daffb4 7c57b388 ISATQ!AtqPoolThread+0x40
03 02daffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 12
System Thread ID: 50c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made
# ChildEBP RetAddr
00 0312feb8 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
01 0312fee4 77d31394 KERNEL32!GetQueuedCompletionStatus+0x27
02 0312ff20 77d3e93f RPCRT4!COMMON_ProcessCalls+0x9e
03 0312ff74 77d3e8c2 RPCRT4!LOADABLE_TRANSPORT::ProcessIOEvents+0x99
04 0312ff78 77d35924 RPCRT4!ProcessIOEventsWrapper+0x9
05 0312ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
06 0312ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
07 0312ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 13
System Thread ID: a84
Kernel Time: 0:0:0.15
User Time: 0:0:0.0
*** WARNING: Unable to verify checksum for C:\WINNT\system32\php4ts.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\WINNT\system32\php4ts.dll -
Thread Type: Other
# ChildEBP RetAddr
00 1b3bff40 031eed95 USER32!NtUserGetMessage+0xb
WARNING: Stack unwind information not available. Following frames may be
wrong.
01 1b3bffb4 7c57b388 php4ts!zend_timeout+0x195
02 1b3bffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 14
System Thread ID: 700
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Idle ASP thread
# ChildEBP RetAddr
00 1bbefd54 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
01 1bbefd7c 7c57b3db KERNEL32!WaitForSingleObjectEx+0x71
02 1bbefd8c 7878db85 KERNEL32!WaitForSingleObject+0xf
03 1bbeffb4 7c57b388 COMSVCS!PingThread+0xf5
04 1bbeffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 15
System Thread ID: 648
Kernel Time: 0:0:0.0
User Time: 0:0:0.15
Thread Type: Other
# ChildEBP RetAddr
00 1c0aff88 751a4848 ntdll!ZwWaitForMultipleObjects+0xb
01 1c0affb4 7c57b388 NETAPI32!NetbiosWaiter+0x71
02 1c0affec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 16
System Thread ID: 32c
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 1c1eff80 74fd6363 ntdll!ZwRemoveIoCompletion+0xb
01 1c1effb4 7c57b388 msafd!SockAsyncThread+0x52
02 1c1effec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 17
System Thread ID: a58
Kernel Time: 0:0:1.343
User Time: 0:0:0.234
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made
# ChildEBP RetAddr
00 2681fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
01 2681ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
02 2681ff78 77d359c3 RPCRT4!RecvLotsaCallsWrapper+0x9
03 2681ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x11f
04 2681ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
05 2681ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 18
System Thread ID: a8c
Kernel Time: 0:0:2.0
User Time: 0:0:0.671
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made
# ChildEBP RetAddr
00 26eefe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
01 26eeff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
02 26eeff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
03 26eeffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
04 26eeffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
05 26eeffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 19
System Thread ID: 35c
Kernel Time: 0:0:0.375
User Time: 0:0:0.125
Thread Type: Possible ASP page. Possible DCOM activity
Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
Continuing with other analysis.

No remote call being made
# ChildEBP RetAddr
00 00e5fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
01 00e5ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
02 00e5ff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
03 00e5ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
04 00e5ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
05 00e5ffec 00000000 KERNEL32!BaseThreadStart+0x52




Thread ID: 20
System Thread ID: 248
Kernel Time: 0:0:0.0
User Time: 0:0:0.0
Thread Type: Other
# ChildEBP RetAddr
00 0129ff60 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
01 0129ff88 77ab510c KERNEL32!WaitForSingleObjectEx+0x71
02 0129ffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x40
03 0129ffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
04 0129ffec 00000000 KERNEL32!BaseThreadStart+0x52

*****

Dump name is formatted as: PID-Timestamp.dmp

Creating C:\iisstate\output\2308-1100530935.dmp - mini user dump

*****

 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
patfilot

External


Since: Aug 24, 2003
Posts: 1478



(Msg. 2) Posted: Mon Nov 15, 2004 10:15 am
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

IISState doesn't monitor memory, so it is not the appropriate tool for this.
I can say, however, that at the time the log was taken, there was no
activity on the server and that 200MB is not a lot of memory to be
committed.

Pat

"Thomas Eiszler" <teiszler RemoveThis @notifycorp.com> wrote in message
news:uSoPIYyyEHA.2676@TK2MSFTNGP12.phx.gbl...
 > Throughout the course of writing a php page that calls a COM dll I
 > experienced errors that I believe were related to some sort of memory
 > leak.
 > Now when I simply goto my localhost (without even going to the php page
 > that
 > loads the COM object), the dllhost process immediately commits over 200MB
 > of
 > memory. I am running Win2k SP4. Any help is greatly appreciated.
 >
 > Opened log file 'C:\iisstate\output\IISState-2308.log'
 >
 > ***********************
 > Starting new log output
 > IISState version 3.3.1
 >
 > Mon Nov 15 10:02:04 2004
 >
 > OS = Windows 2000
 > Executable: dllhost.exe
 > PID = 2308
 >
 > Note: Thread times are formatted as HH:MM:SS.ms
 >
 > ***********************
 >
 >
 >
 >
 > Thread ID: 0
 > System Thread ID: 8e8
 > Kernel Time: 0:0:0.15
 > User Time: 0:0:0.15
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 0006fd28 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
 > 01 0006fd50 7c57b3db KERNEL32!WaitForSingleObjectEx+0x71
 > 02 0006fd60 77aaa701 KERNEL32!WaitForSingleObject+0xf
 > 03 0006fd80 77aa9f0f
 > ole32!CSurrogateProcessActivator::WaitForSurrogateTimeout+0x4f
 > 04 0006fd9c 01001230 ole32!CoRegisterSurrogateEx+0x169
 > 05 0006ff24 010014c6 dllhost!WinMain+0xb0
 > 06 0006ffc0 7c59893d dllhost!WinMainCRTStartup+0x156
 > 07 0006fff0 00000000 KERNEL32!BaseProcessStart+0x3d
 >
 >
 >
 >
 > Thread ID: 1
 > System Thread ID: 864
 > Kernel Time: 0:0:5.468
 > User Time: 0:0:1.125
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > No remote call being made
 >
 > # ChildEBP RetAddr
 > 00 00d9fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
 > 01 00d9ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
 > 02 00d9ff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 00d9ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
 > 04 00d9ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
 > 05 00d9ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 2
 > System Thread ID: a9c
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 00ddff5c 7c59a243 ntdll!NtDelayExecution+0xb
 > 01 00ddff7c 7c59a20e KERNEL32!SleepEx+0x32
 > 02 00ddff88 77ab8ffb KERNEL32!Sleep+0xb
 > 03 00ddff90 77ab50ee ole32!CROIDTable::WorkerThreadLoop+0xc
 > 04 00ddffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x22
 > 05 00ddffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
 > 06 00ddffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 3
 > System Thread ID: 8e4
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 00e1ff30 77abbad5 USER32!NtUserGetMessage+0xb
 > 01 00e1ff70 77abba23 ole32!CDllHost::STAWorkerLoop+0x40
 > 02 00e1ff8c 77abb95e ole32!CDllHost::WorkerThread+0xc2
 > 03 00e1ff90 77ab50ee ole32!DLLHostThreadEntry+0x9
 > 04 00e1ffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x22
 > 05 00e1ffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
 > 06 00e1ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 4
 > System Thread ID: a7c
 > Kernel Time: 0:0:0.46
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 0125fc54 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
 > 01 0125fc80 6de8b9d0 KERNEL32!GetQueuedCompletionStatus+0x27
 > 02 0125fd94 6de8b908 TxfAux!WORK_QUEUE::WorkerLoop+0xa0
 > 03 0125ffb4 7c57b388 TxfAux!WORK_QUEUE::ThreadLoop+0x58
 > 04 0125ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 5
 > System Thread ID: a1c
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Idle ASP thread
 > # ChildEBP RetAddr
 > 00 01f5ff08 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
 > 01 01f5ff58 7c59a0c2 KERNEL32!WaitForMultipleObjectsEx+0xea
 > 02 01f5ff70 787f58ce KERNEL32!WaitForMultipleObjects+0x17
 > 03 01f5ffb4 7c57b388 COMSVCS!CEventDispatcher::PushEvents+0x4e
 > 04 01f5ffc0 01e3efe0 KERNEL32!BaseThreadStart+0x52
 > WARNING: Frame IP not in any known module. Following frames may be wrong.
 > 05 017288f0 01ee6000 0x1e3efe0
 > 06 017288f0 01ee6000 0x1ee6000
 > 07 017276d0 01ee4000 0x1ee6000
 > 08 017287b0 01ee2000 0x1ee4000
 > 09 01728530 01f0e000 0x1ee2000
 > 0a 01727f18 01f0c000 0x1f0e000
 > 0b 01728e18 01f0a000 0x1f0c000
 > 0c 01727e28 01f08000 0x1f0a000
 > 0d 01728a58 01f02000 0x1f08000
 > 0e 013f7b88 01f00000 0x1f02000
 > 0f 01727ea0 01efc000 0x1f00000
 > 10 017274c8 01e90000 0x1efc000
 > 11 017286e8 0186a000 0x1e90000
 > 12 01727d60 01714000 0x186a000
 > 13 013f7c00 01744000 0x1714000
 > 14 00074028 00cbe000 0x1744000
 > 15 017282b0 01e8e000 0xcbe000
 > 16 01727068 01884000 0x1e8e000
 > 17 01728e40 01882000 0x1884000
 > 18 01727e50 0187e000 0x1882000
 > 19 01728ff8 0187c000 0x187e000
 > 1a 017270b8 01878000 0x187c000
 > 1b 017287d8 01876000 0x1878000
 > 1c 017262f8 01870000 0x1876000
 > 1d 01728120 0186e000 0x1870000
 > 1e 01728e90 01830000 0x186e000
 > 1f 01727158 0182e000 0x1830000
 > 20 01726eb0 0171e000 0x182e000
 > 21 01728d50 01eda000 0x171e000
 > 22 01728670 01ebe000 0x1eda000
 > 23 017271f8 01eba000 0x1ebe000
 > 24 01726ed8 01ea0000 0x1eba000
 > 25 01726820 0172a000 0x1ea0000
 > 26 017271a8 016f6000 0x172a000
 > 27 013f7930 016e4000 0x16f6000
 > 28 01728f30 01efe000 0x16e4000
 > 29 01727e78 01efa000 0x1efe000
 > 2a 01727e00 01ef8000 0x1efa000
 > 2b 017260c8 01ea2000 0x1ef8000
 > 2c 01729098 01e9e000 0x1ea2000
 > 2d 01729070 01e9c000 0x1e9e000
 > 2e 01728f58 01824000 0x1e9c000
 > 2f 01728cd8 01820000 0x1824000
 > 30 01729048 01e92000 0x1820000
 > 31 01727ec8 01e8c000 0x1e92000
 >
 >
 >
 >
 > Thread ID: 6
 > System Thread ID: 9b4
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > Remote call is either to a MTA object or object not initialized. Also,
 > possible utility thread.
 > DCOM call being made to Process ID: 2220
 > Waiting on thread id: ffffffff
 >
 > # ChildEBP RetAddr
 > 00 01f9fb68 77d4256d ntdll!ZwRequestWaitReplyPort+0xb
 > 01 01f9fb94 77d3ac56 RPCRT4!LRPC_CCALL::SendReceive+0x11e
 > 02 01f9fba0 77b25b87 RPCRT4!I_RpcSendReceive+0x2c
 > 03 01f9fbc0 77b25a52 ole32!ThreadSendReceive+0xef
 > 04 01f9fbd8 77b22ab6
 > ole32!CRpcChannelBuffer::SwitchAptAndDispatchCall+0x14f
 > 05 01f9fc18 77b258c6 ole32!CRpcChannelBuffer::SendReceive2+0x96
 > 06 01f9fc28 77a6cb5d ole32!CRpcChannelBuffer::SendReceive+0x11
 > 07 01f9fc88 77ab74c3 ole32!CAptRpcChnl::SendReceive+0xa9
 > 08 01f9fce0 77d94c1a ole32!CCtxComChnl::SendReceive+0x124
 > 09 01f9fcfc 77d9487d RPCRT4!NdrProxySendReceive+0x4c
 > 0a 01f9ff44 77d95136 RPCRT4!NdrClientCall2+0x4f5
 > 0b 01f9ff60 77d46e75 RPCRT4!ObjectStublessClient+0x76
 > 0c 01f9ff70 787f5818 RPCRT4!ObjectStubless+0xf
 > 0d 01f9ffb4 7c57b388
 > COMSVCS!CEventDispatcher::GetEventServerInfoThread+0x118
 > 0e 01f9ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 7
 > System Thread ID: 300
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Idle ASP thread
 > # ChildEBP RetAddr
 > 00 01fdfee0 7c59a243 ntdll!NtDelayExecution+0xb
 > 01 01fdff00 7c59a20e KERNEL32!SleepEx+0x32
 > 02 01fdff0c 787d12aa KERNEL32!Sleep+0xb
 > 03 01fdff7c 780085bc COMSVCS!PostData+0xf2
 > 04 01fdffb4 7c57b388 MSVCRT!_endthreadex+0xc1
 > 05 01fdffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 8
 > System Thread ID: a40
 > Kernel Time: 0:0:1.140
 > User Time: 0:0:0.765
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 02a6fe5c 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
 > 01 02a6feac 77e119e6 KERNEL32!WaitForMultipleObjectsEx+0xea
 > 02 02a6ff08 77e11ace USER32!MsgWaitForMultipleObjectsEx+0x153
 > 03 02a6ff24 6e5a5a7c USER32!MsgWaitForMultipleObjects+0x1d
 > 04 02a6ff7c 780085bc IISRTL!SchedulerWorkerThread+0xa7
 > 05 02a6ffb4 7c57b388 MSVCRT!_endthreadex+0xc1
 > 06 02a6ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 9
 > System Thread ID: 894
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 02aafe5c 7c59a1af ntdll!ZwWaitForMultipleObjects+0xb
 > 01 02aafeac 77e119e6 KERNEL32!WaitForMultipleObjectsEx+0xea
 > 02 02aaff08 77e11ace USER32!MsgWaitForMultipleObjectsEx+0x153
 > 03 02aaff24 6e5a5a7c USER32!MsgWaitForMultipleObjects+0x1d
 > 04 02aaff7c 780085bc IISRTL!SchedulerWorkerThread+0xa7
 > 05 02aaffb4 7c57b388 MSVCRT!_endthreadex+0xc1
 > 06 02aaffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 10
 > System Thread ID: 6b4
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: HTTP Listener
 > # ChildEBP RetAddr
 > 00 02d6ff50 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
 > 01 02d6ff7c 6d702957 KERNEL32!GetQueuedCompletionStatus+0x27
 > 02 02d6ffb4 7c57b388 ISATQ!AtqPoolThread+0x40
 > 03 02d6ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 11
 > System Thread ID: 8b8
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: HTTP Listener
 > # ChildEBP RetAddr
 > 00 02daff50 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
 > 01 02daff7c 6d702957 KERNEL32!GetQueuedCompletionStatus+0x27
 > 02 02daffb4 7c57b388 ISATQ!AtqPoolThread+0x40
 > 03 02daffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 12
 > System Thread ID: 50c
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > No remote call being made
 > # ChildEBP RetAddr
 > 00 0312feb8 7c5853d7 ntdll!ZwRemoveIoCompletion+0xb
 > 01 0312fee4 77d31394 KERNEL32!GetQueuedCompletionStatus+0x27
 > 02 0312ff20 77d3e93f RPCRT4!COMMON_ProcessCalls+0x9e
 > 03 0312ff74 77d3e8c2 RPCRT4!LOADABLE_TRANSPORT::ProcessIOEvents+0x99
 > 04 0312ff78 77d35924 RPCRT4!ProcessIOEventsWrapper+0x9
 > 05 0312ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
 > 06 0312ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
 > 07 0312ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 13
 > System Thread ID: a84
 > Kernel Time: 0:0:0.15
 > User Time: 0:0:0.0
 > *** WARNING: Unable to verify checksum for C:\WINNT\system32\php4ts.dll
 > *** ERROR: Symbol file could not be found. Defaulted to export symbols
 > for
 > C:\WINNT\system32\php4ts.dll -
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 1b3bff40 031eed95 USER32!NtUserGetMessage+0xb
 > WARNING: Stack unwind information not available. Following frames may be
 > wrong.
 > 01 1b3bffb4 7c57b388 php4ts!zend_timeout+0x195
 > 02 1b3bffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 14
 > System Thread ID: 700
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Idle ASP thread
 > # ChildEBP RetAddr
 > 00 1bbefd54 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
 > 01 1bbefd7c 7c57b3db KERNEL32!WaitForSingleObjectEx+0x71
 > 02 1bbefd8c 7878db85 KERNEL32!WaitForSingleObject+0xf
 > 03 1bbeffb4 7c57b388 COMSVCS!PingThread+0xf5
 > 04 1bbeffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 15
 > System Thread ID: 648
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.15
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 1c0aff88 751a4848 ntdll!ZwWaitForMultipleObjects+0xb
 > 01 1c0affb4 7c57b388 NETAPI32!NetbiosWaiter+0x71
 > 02 1c0affec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 16
 > System Thread ID: 32c
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 1c1eff80 74fd6363 ntdll!ZwRemoveIoCompletion+0xb
 > 01 1c1effb4 7c57b388 msafd!SockAsyncThread+0x52
 > 02 1c1effec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 17
 > System Thread ID: a58
 > Kernel Time: 0:0:1.343
 > User Time: 0:0:0.234
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > No remote call being made
 > # ChildEBP RetAddr
 > 00 2681fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
 > 01 2681ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
 > 02 2681ff78 77d359c3 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 2681ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x11f
 > 04 2681ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
 > 05 2681ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 18
 > System Thread ID: a8c
 > Kernel Time: 0:0:2.0
 > User Time: 0:0:0.671
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > No remote call being made
 > # ChildEBP RetAddr
 > 00 26eefe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
 > 01 26eeff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
 > 02 26eeff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 26eeffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
 > 04 26eeffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
 > 05 26eeffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 19
 > System Thread ID: 35c
 > Kernel Time: 0:0:0.375
 > User Time: 0:0:0.125
 > Thread Type: Possible ASP page. Possible DCOM activity
 > Executing Page: ASP.dll symbols not found. Unable to locate ASP page.
 > Continuing with other analysis.
 >
 > No remote call being made
 > # ChildEBP RetAddr
 > 00 00e5fe24 77d37ba7 ntdll!ZwReplyWaitReceivePortEx+0xb
 > 01 00e5ff74 77d37b4c RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x74
 > 02 00e5ff78 77d35924 RPCRT4!RecvLotsaCallsWrapper+0x9
 > 03 00e5ffa8 77d358d6 RPCRT4!BaseCachedThreadRoutine+0x4f
 > 04 00e5ffb4 7c57b388 RPCRT4!ThreadStartRoutine+0x18
 > 05 00e5ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 >
 >
 >
 > Thread ID: 20
 > System Thread ID: 248
 > Kernel Time: 0:0:0.0
 > User Time: 0:0:0.0
 > Thread Type: Other
 > # ChildEBP RetAddr
 > 00 0129ff60 7c599fe4 ntdll!ZwWaitForSingleObject+0xb
 > 01 0129ff88 77ab510c KERNEL32!WaitForSingleObjectEx+0x71
 > 02 0129ffa8 77ab5046 ole32!CRpcThread::WorkerLoop+0x40
 > 03 0129ffb4 7c57b388 ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x1a
 > 04 0129ffec 00000000 KERNEL32!BaseThreadStart+0x52
 >
 > *****
 >
 > Dump name is formatted as: PID-Timestamp.dmp
 >
 > Creating C:\iisstate\output\2308-1100530935.dmp - mini user dump
 >
 > *****
 >
 ><!-- ~MESSAGE_AFTER~ -->

 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
teiszler

External


Since: Nov 15, 2004
Posts: 4



(Msg. 3) Posted: Mon Nov 15, 2004 5:06 pm
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Well if I put the two .dlls (one is the ATL COM .dll and the other is the
dll that is wrapped by the ATL COM .dll so that I can use its functions from
php) and the php files onto another test machine (also Win2k, IIS 5) this
problem doesn't happen. Could it possibly have something to do with the COM
..dll not unregistering? I built the .dll on this machine in VC++ 6 and that
is really the only difference between this machine and the other one I
tested on. I have used WinDBG and other debug tools to try and view the
dumps that were generated during my testing and they all pointed to
functions in ntdll.dll like RtlFreeHeap. I use unset to delete the COM
object in php after I am done using the functions of the dll. I hope this
helps explain my situation better.

Thansk for your response Pat and hopefully you will have some more advice.

Thanks.
 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
patfilot

External


Since: Aug 24, 2003
Posts: 1478



(Msg. 4) Posted: Mon Nov 15, 2004 5:06 pm
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

You need to look further down the stack than RtlFreeHeap, etc. Those are
the memory API's and I would expect to see them in a memory analysis, the
important bit is _who_ is calling them.

As to why it doesn't happen on another machine, I can't say. It could be
that there is only 1 code path that leaks and that on the other test machine
this code path is either not being hit or is hit much less frequently. This
is often the case where you have something like:

try
{
AllocateMemory
...Do Cool Stuff...
Release Memory
}
catch(...)
{
AllocateMoreMemory
Write An Error
FreeMoreMemory
}
return

In this case, if the try failed during the ...Do Cool Stuff... section, the
memory would leak, but otherwise you would be fine. This happens more often
than you would think (so often so, that one method of tracking down leaks is
to grep the try blocks and make sure catch blocks clean up).

If you have a profiler available (VTune?), you may be able to identify the
culprit.

Pat

"Thomas Eiszler" <teiszler.DeleteThis@notifycorp.com> wrote in message
news:O5XFo91yEHA.2040@tk2msftngp13.phx.gbl...
 > Well if I put the two .dlls (one is the ATL COM .dll and the other is the
 > dll that is wrapped by the ATL COM .dll so that I can use its functions
 > from
 > php) and the php files onto another test machine (also Win2k, IIS 5) this
 > problem doesn't happen. Could it possibly have something to do with the
 > COM
 > .dll not unregistering? I built the .dll on this machine in VC++ 6 and
 > that
 > is really the only difference between this machine and the other one I
 > tested on. I have used WinDBG and other debug tools to try and view the
 > dumps that were generated during my testing and they all pointed to
 > functions in ntdll.dll like RtlFreeHeap. I use unset to delete the COM
 > object in php after I am done using the functions of the dll. I hope this
 > helps explain my situation better.
 >
 > Thansk for your response Pat and hopefully you will have some more advice.
 >
 > Thanks.
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
teiszler

External


Since: Nov 15, 2004
Posts: 4



(Msg. 5) Posted: Tue Nov 16, 2004 9:19 am
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

The stack doesn't ever include any of the functions in the ATL COM dll that
I wrote. I might not be getting a full stack trace, but the only things
that appear in the stack are calls from ntdll and ole. I don't use new or
delete and I only create one class object whose destructor should be called
when it goes out of scope. All the other variables I use are basic types and
their scope is limited to functions.
As for the discrepancy between this and the other machine, my machine
doesn't even have to run a single webpage from IIS and yet dllhost.exe
starts and immediately consumes around 250 MB. This happens without me going
to any page on localhost and no one else could be accessing those pages. I
have tried all code paths on both machines (There are only 4 functions and I
called them all in both scenarios).

Thanks again.
 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
patfilot

External


Since: Aug 24, 2003
Posts: 1478



(Msg. 6) Posted: Tue Nov 16, 2004 9:19 am
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

You aren't getting full stacks. 'new' and 'delete' are in the c-runtime,
but would eventually call into HeapAlloc/FreeHeap. The ATL wrappers for
memory (e.g. smart pointers) also eventually call into either the
HeapAlloc/FreeHeap or VirtualAlloc/VirtualFree API's.

I would recommend contacting MS Developer support. They can help track down
the problem. It may be a bug in COM+ (OLE32/RPCRT4), or it could just be
something very subtle in your code.



Pat

"Thomas Eiszler" <teiszler RemoveThis @notifycorp.com> wrote in message
news:uwzLLd%23yEHA.2036@TK2MSFTNGP12.phx.gbl...
 > The stack doesn't ever include any of the functions in the ATL COM dll
 > that
 > I wrote. I might not be getting a full stack trace, but the only things
 > that appear in the stack are calls from ntdll and ole. I don't use new or
 > delete and I only create one class object whose destructor should be
 > called
 > when it goes out of scope. All the other variables I use are basic types
 > and
 > their scope is limited to functions.
 > As for the discrepancy between this and the other machine, my machine
 > doesn't even have to run a single webpage from IIS and yet dllhost.exe
 > starts and immediately consumes around 250 MB. This happens without me
 > going
 > to any page on localhost and no one else could be accessing those pages. I
 > have tried all code paths on both machines (There are only 4 functions and
 > I
 > called them all in both scenarios).
 >
 > Thanks again.
 >
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
teiszler

External


Since: Nov 15, 2004
Posts: 4



(Msg. 7) Posted: Tue Nov 16, 2004 11:31 am
Post subject: Re: DLLHOST High Mem Usage [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Thanks for all your help. How do I connect MSDev support and what will I
need to give to them?
 >> Stay informed about: DLLHOST High Mem Usage 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
DLLHost with high memory usage - My IIS memory usage gradually increases and after 3 or 4 weeks, the site goes down and restarts. Can anyone recommend any tools to see what handles are alive on the server and how much memory is being consumed by the handle. I've been trying to use..

High CPU for dllhost.exe with IIS 6.0 - Hello On a machine with Windows Server 2003 where our web application (in ASP 6.0 and using VB 6.0 COM+ applications) are running, we periodically see a high CPU usage for the dllhost.exe process. The contents of iisstate are as follows. I...

High CPU Usage - I`m using IIS 4 on Win NT and from time to time the inetinfo.exe CPU usage reaches 100% and makes everything extremely slow. Someone has told me that it is more likely that there is some code running on my server that is taking all of the cpu time...

High CPU Usage - I`m using IIS 4 on Win NT and from time to time the inetinfo.exe CPU usage reaches 100% and makes everything extremely slow. Is there a patch I can install on my IIS 4 to handle this problem? Thx, Pete

High CPU usage - Once a while my web server had a high CPU utility which caused unaccessable to the company website. Under the 'Windows Task Manager', an 'Image Name' inetinfo.exe caused the high CPU uitility. I had to either stop & restart the WWW in the services or...
   Web Hosting and Web Master Forums (Home) -> IIS All times are: Pacific Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]