I got the following question in my Getting started with windbg – post and I thought it might be worth posting the replies in a separate article:
about those threads with an ID of XXXX, should they go away after certain amount of idle time like 2 minutes? I am trouble shooting an application while the application should sit idle (because of no stimulation), however it is still using quite some CPU time and and threadpool threads, where it should not. So I created an adplus dump when it is sitting idle, and I found that there are many threads with ID XXXX, and I created a dump file again after 15 minutes, again, it still have the exact same XXXX threads. All those threads are completion port threads, and I wonder why they did not get recycled?
Also, when doing a ‘~*e !clrstack’, most of the worker threads and completion port threads are showing “Failed to start stack walk: 80004005”. Is there a way to show the stack for those threads, because those are the threads I am interested in.
The GC will be triggered when you’re allocating memory. If your application is inactive, then so is the Garbage Collector. Even if you’re making a few, random allocations they still may not be enough to trigger a GC, so this is not at all unexpected.
The “Failed to start stack walk: 80004005”-error is displayed when the thread did contain a managed stack, but no longer does.