If a process loads a lots of dll & if that process took 100% CPU Usage,
is there any way to find out which dll(or module) eating the CPU resource.
Is there any thing like CPU time taken by the process for dlls or modules?

Thanks & Regards,
Muthu Nivas.H

Re: How to find the exact dll which cause 100% CPU usage? by Oleg

Oleg
Fri Oct 01 05:06:24 CDT 2004


> If a process loads a lots of dll & if that process took 100% CPU Usage,
> is there any way to find out which dll(or module) eating the CPU resource.
> Is there any thing like CPU time taken by the process for dlls or modules?
>

If you are interested in tracking down the reason of a suspected infinite loop
(not in measuring performance bottlenecks), WinDbg documentation
contains a good article about it - "Tracking down a processor hog".

http://www.microsoft.com/whdc/ddk/debugging/default.mspx

You can use the same approach with any other debugger
(identify the offending thread with PerfMon).

Regards,
Oleg






Re: How to find the exact dll which cause 100% CPU usage? by Scott

Scott
Fri Oct 01 07:45:55 CDT 2004

Muthu Nivas wrote:

> If a process loads a lots of dll & if that process took 100% CPU Usage,
> is there any way to find out which dll(or module) eating the CPU resource.
> Is there any thing like CPU time taken by the process for dlls or modules?
>
> Thanks & Regards,
> Muthu Nivas.H

While running the process in the debugger you can use the debugger's
Break menu command to stop it. Then look at the stack window to see
where it was executing.

--
Scott McPhillips [VC++ MVP]