Bug 54979 - VS debugger shows some threads as "<Thread Pool>" thread name even though they are not
Summary: VS debugger shows some threads as "<Thread Pool>" thread name even though the...
Status: RESOLVED INVALID
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Debugger ()
Version: 4.4.0 (15.1)
Hardware: PC Windows
: Normal normal
Target Milestone: 15.3
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2017-04-10 16:48 UTC by philip
Modified: 2017-05-22 14:35 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description philip 2017-04-10 16:48:50 UTC
Create a thread with this pattern:

				summaryThread = new Thread(Run)
				{
					Name = "summaryThread",
					IsBackground = false,
					Priority = ThreadPriority.Normal
				};
				summaryThread.Start();

The problem seems to happen after an await VS debugger shows wrong info about the thread:

		public async void Run()
		{
                    Debugger.Break();        // here VS debugger shows thread name as "summaryThread"
		    await Task.Delay(20);
                    Debugger.Break();        // here VS debugger shows thread name as "<Thread Pool>"
                }
Comment 1 philip 2017-05-22 14:35:18 UTC
sorry I thought it was using Task.Delay(20).Wait().  Closing this report.