Reputation: 19986
One of my threads in the process is burning one CPU core to the full extent. 8 cores, 12,5% CPU used. Look at this (procexp screenshot)
http://dl.dropbox.com/u/10020780/scr1.PNG
Another thing that bothers me it Start Address
of 0x0
!?!?
I am trying to find the thread in the list provided with the VS2008 Thread View, but not a single thread there (or I have overlooked) has a tight loop (without Sleep()
) or a clear indication of trouble.
Any hints?
CASE UPDATE:
It seems like I'm beyond my code realm on this one; I'll post a pictures obtained with STACK button, so you can maybe have some hunch on the issue at hand.
First situation
http://dl.dropbox.com/u/10020780/smallstack.PNG
Second situation (same thread, I get this two alternating)
http://dl.dropbox.com/u/10020780/largerstack.PNG
Guys, where am I? I do use Windows Media, Sockets, ...
Upvotes: 0
Views: 139
Reputation: 19986
Humph - after lot of headbanging, I figured out that (I should do that sooner) thread id from procexp can be found inside visual studio as well - and found the thread that caused the problem. It was tight loop, that I resolved with Sleep(10).
Upvotes: 0
Reputation: 4144
have you tried to take a hang dump with Adplus, and running the !runaway commnand in WinDbg ? this will show you for sure what thread, and then you can use !clrstack to get what the thread aws doing.
Upvotes: 1