dotnet/roslyn

InvalidOperationException while adjusting receiver namespace

Open

#8,610 建立於 2016年2月11日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)C# (20,414 star) (4,257 fork)batch import
Area-CompilersBughelp wanted

描述

Microsoft.CodeAnalysis.VisualBasic.Symbols.NamespaceSymbol Shrink(System.Collections.Generic.IEnumerable`1[Microsoft.CodeAnalysis.VisualBasic.Symbols.NamespaceSymbol])
Microsoft.CodeAnalysis.VisualBasic.BoundNamespaceExpression AdjustReceiverNamespace(Microsoft.CodeAnalysis.VisualBasic.BoundNamespaceExpression, Microsoft.CodeAnalysis.ArrayBuilder`1[Microsoft.CodeAnalysis.VisualBasic.Symbol])
Microsoft.CodeAnalysis.VisualBasic.BoundExpression BindNamespaceOrTypeOrExpressionSyntaxForSemanticModel(Microsoft.CodeAnalysis.VisualBasic.Syntax.ExpressionSyntax, Microsoft.CodeAnalysis.DiagnosticBag)
Microsoft.CodeAnalysis.VisualBasic.BoundNode Bind(Microsoft.CodeAnalysis.VisualBasic.Binder, Microsoft.CodeAnalysis.VisualBasic.VisualBasicSyntaxNode, Microsoft.CodeAnalysis.DiagnosticBag)
System.Collections.Immutable.ImmutableArray`1[Microsoft.CodeAnalysis.VisualBasic.BoundNode] GetBoundNodes(Microsoft.CodeAnalysis.VisualBasic.VisualBasicSyntaxNode)
Microsoft.CodeAnalysis.VisualBasic.BoundNode GetUpperBoundNode(Microso...

The stack isn't great since it comes from telemetry. It should be better in Dev14U2.

~12K hits in 10 days.

貢獻者指南

技術棧
csharp
領域
tooling
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Understanding of .NET compiler internalsKnowledge of Visual Basic bindingFamiliarity with Roslyn source codeDebugging skills
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
The issue reports an InvalidOperationException during namespace adjustment in the Visual Basic binder. The stack trace points to the Shrink and AdjustReceiverNamespace methods in the Visual Basic Symbols namespace. To fix this, one should first find a minimal reproducer, possibly by examining the telemetry context or creating a code sample that triggers the crash. Then, investigate the BindNamespaceOrTypeOrExpressionSyntaxForSemanticModel method and the subsequent calls to understand the invalid state. The high crash count (12K hits) suggests a common scenario, so focusing on common VB files with complex namespace structures may help. Consider adding an assertion or null check in the Shrink method to handle the invalid operation gracefully.