memory in svchost.exe

[dave xnet]

Hello, if I'm trying to troubleshoot an svchost.exe that's using a
lot of memory, I can use the tasklist command or process explorer to
identify the services running in each svchost.

How can I tell within the svchost, how much memory each
service is using ? Neither the Task Manager, Tasklist CMD or
Process Explorer seems to show this info.

TIA,
Dave

 

[Ace]

In Process Explorer you can double click a process to bring up it's
properties, and find it's memory usage there on one of the tabs.
Processes that act as the parent for others, such as svchost.exe you
should be able to fold open by clicking the + next to it's name.
Then select the child process you wish to check.
If there is no + next to a process, then that process is not running any
other child processes.

 

[dave xnet]

In Process Explorer you can double click a process to bring up it's
properties, and find it's memory usage there on one of the tabs.
Processes that act as the parent for others, such as svchost.exe you
should be able to fold open by clicking the + next to it's name.
Then select the child process you wish to check.
If there is no + next to a process, then that process is not running any
other child processes.

I don't see it. It shows svchost to be a chld of services.exe,
but doesn't list any children under svchost.exe.

If you open it you can get a list of threads, but mem use is
not shown. Perhaps there's a technical answer why it's not there -
it sure would be useful.

Dave

 

[John John]

Hello, if I'm trying to troubleshoot an svchost.exe that's using a
lot of memory, I can use the tasklist command or process explorer to
identify the services running in each svchost.

How can I tell within the svchost, how much memory each
service is using ? Neither the Task Manager, Tasklist CMD or
Process Explorer seems to show this info.

You will have to create Isolated Processes or create Isolated Service
Groups, either method would allow you to find the culprit. It's a bit
easier to create an Isolated Process than it is to create an Isolated
Process Group. Back up your registry before you begin and make sure
that you keep track of what you do, write it down! It will make it
easier to undo your changes as you eliminate successive processes. See
here for more information:

Getting Started with SVCHOST.EXE Troubleshooting
http://blogs.technet.com/askperf/ar...started-with-svchost-exe-troubleshooting.aspx

John

 

[dave xnet]

You will have to create Isolated Processes or create Isolated Service
Groups, either method would allow you to find the culprit. It's a bit
easier to create an Isolated Process than it is to create an Isolated
Process Group. Back up your registry before you begin and make sure
that you keep track of what you do, write it down! It will make it
easier to undo your changes as you eliminate successive processes. See
here for more information:

Getting Started with SVCHOST.EXE Troubleshooting
http://blogs.technet.com/askperf/ar...started-with-svchost-exe-troubleshooting.aspx

John

John, thanks for the pointer.
Dave

 

[John John]

John, thanks for the pointer.

You're welcome.

John