Exception while parsing: Document is not part of the workspace

[KirillOsenkov]

VSMac 7.6.5.20

ERROR [2018-09-15 21:40:36Z]: Exception while parsing: System.ArgumentException: '<Documentccec545d-e7ce-4840-bb4c-850c5effeb15>' is not part of the workspace.
  at Microsoft.CodeAnalysis.Workspace.CheckDocumentIsInCurrentSolution (Microsoft.CodeAnalysis.DocumentId documentId) [0x00025] in /_/src/Workspaces/Core/Portable/Workspace/Workspace.cs:1810 
  at Microsoft.CodeAnalysis.Workspace.OnAnyDocumentTextChanged (Microsoft.CodeAnalysis.DocumentId documentId, Microsoft.CodeAnalysis.Text.SourceText newText, Microsoft.CodeAnalysis.PreservationMode mode, System.Action`1[T] checkIsInCurrentSolution, System.Func`3[T1,T2,TResult] getRelatedDocuments, System.Func`5[T1,T2,T3,T4,TResult] updateSolutionWithText, Microsoft.CodeAnalysis.WorkspaceChangeKind changeKind, System.Boolean isCodeDocument) [0x00015] in /_/src/Workspaces/Core/Portable/Workspace/Workspace.cs:902 
  at Microsoft.CodeAnalysis.Workspace.OnDocumentTextChanged (Microsoft.CodeAnalysis.DocumentId documentId, Microsoft.CodeAnalysis.Text.SourceText newText, Microsoft.CodeAnalysis.PreservationMode mode) [0x00000] in /_/src/Workspaces/Core/Portable/Workspace/Workspace.cs:857 
  at Microsoft.CodeAnalysis.Workspace.ApplyDocumentTextChanged (Microsoft.CodeAnalysis.DocumentId id, Microsoft.CodeAnalysis.Text.SourceText text) [0x00000] in /_/src/Workspaces/Core/Portable/Workspace/Workspace.cs:1617 
  at MonoDevelop.Ide.TypeSystem.MonoDevelopWorkspace.InformDocumentTextChange (Microsoft.CodeAnalysis.DocumentId id, Microsoft.CodeAnalysis.Text.SourceText text) [0x00000] in /Users/vsts/agent/2.140.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.TypeSystem/MonoDevelopWorkspace.cs:279 
  at MonoDevelop.Ide.TypeSystem.TypeSystemService+<ParseProjection>d__17.MoveNext () [0x001d6] in /Users/vsts/agent/2.140.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Ide.TypeSystem/TypeSystemService.cs:246 

VS bug #685786

[Therzok]

Might be fixed in 7.7, I've done quite a few changes in the locking hierarchy.

[KirillOsenkov]

Is it benign? If there's no user visible impact, no need to port to 7.6. Otherwise if it is harmful, should we port? Not sure if the change that fixes it is easy to tease out from the rest?

[Therzok]

Pretty complicated, the locking hierarchy fixing was tightly coupled to decoupling the components. No 'easy fix' to backport here.

[KirillOsenkov]

OK then if you're confident this is fixed in 7.7 and newer, let's just close this?

[Therzok]

Will validate and see if there are any other races going on.

Symlinks could also cause this which are recently fixed

[Therzok]

Let's close this. Seems fixed to me.