vs-commitizen
vs-commitizen copied to clipboard
Visual Studio crashes in most cases when opening Team Explorer
Describe the bug Visual Studio crashes sometimes when opening Team Explorer after just starting up Visual Studio. My fellow team mates have the same behavior on their machines from time to time. Could it be performance related? When repeating the steps from the reproduction it will not crash after a few retries.
Eventlog shows .NET Runtime error:
Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at Microsoft.VisualStudio.Shell.ThreadHelper.get_JoinableTaskContext() at vs_commitizen.vs2015.VsCommitizenNavigationItem+<UpdateIsVisibleAsync>d__4.MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at vs_commitizen.vs2015.VsCommitizenNavigationItem+<GitService_PropertyChanged>d__3.MoveNext() at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
To Reproduce Steps to reproduce the behavior:
- Start Visual Studio
- Open Recent project (in this case hosted on Azure DevOps / Git-repo)
- Click Connect in the (authentication) dialog that is opening up.
Expected behavior No crash.
Screenshots
If applicable, add screenshots to help explain your problem.
Visual Studio (please complete the following information):
- Professional or Enterprise (same behavior)
- 2019 / 16.2.3