-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime thread names #34276
Comments
I couldn't figure out the best area label to add to this issue. Please help me learn by adding exactly one area label. |
Related dotnet/coreclr#27182 |
The plot thickens; on a different service that I just moved to .NET 5, there are threads named |
Can you attach a debugger/grab a dump and look at the call stacks of those threads? |
I was able to attach a debugger over SSH. First observation: The 'threads' view in Visual Studio shows more unnamed threads that are actually named in So I moved over to |
@macaba not on dotnet-dump. All it can do relates to managed code. The best idea here is to use a native debugger. lldb is usually what we recommend as it can skip over managed frames and if needed you can use SOS commands. |
Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process. This process is part of our issue cleanup automation. |
This issue will now be closed since it had been marked |
Running an application on Ubuntu 18.04.4 LTS under .NET 5 Preview 1 using Server GC, then running
htop
and enabling custom thread names gives me this view:Most of the threads make sense to me, but there seems to be 7 unnamed threads (
GeoVR.RangingSe
) some of which I suspect are GC threads.It would be beneficial if the runtime named these threads.
I would be willing to attempt a pull request but I have no runtime development experience so any hints to where I should be looking in the codebase would be most appreciated.
The text was updated successfully, but these errors were encountered: