Skip to content
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

Creating C# WPF apps crash VS with ArgumentNullException #19351

Closed
mattscheffer opened this issue May 8, 2017 · 9 comments
Closed

Creating C# WPF apps crash VS with ArgumentNullException #19351

mattscheffer opened this issue May 8, 2017 · 9 comments
Assignees
Labels
Area-IDE Bug Resolution-Duplicate The described behavior is tracked in another issue Tenet-Reliability Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner.

Comments

@mattscheffer
Copy link
Contributor

Version Used:
VSUML 26507.1
Steps to Reproduce:

  1. Install VS with .NET Desktop Development
  2. Create a new C# WPF App

Expected Behavior:
Project creates successfully and you are able to work on it.
Actual Behavior:
Project creates followed by crashing VS.

Exception:

CLR: Managed code called FailFast, saying "System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.Runtime.CompilerServices.ConditionalWeakTable`2.TryGetValue(TKey key, TValue& value)
   at System.Runtime.CompilerServices.ConditionalWeakTable`2.GetValue(TKey key, CreateValueCallback createValueCallback)
   at Microsoft.CodeAnalysis.Serialization.ChecksumCache.GetOrCreate(Object value, CreateValueCallback checksumCreator)
   at Microsoft.CodeAnalysis.FindSymbols.SyntaxTreeIndex.<GetChecksumAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.FindSymbols.SyntaxTreeIndex.<PrecalculateAsync>d__51.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService.WorkCoordinator.IncrementalAnalyzerProcessor.<>c__DisplayClass31_1`1.<<RunAnalyzersAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.CodeAnalysis.SolutionCrawler.SolutionCrawlerRegistrationService.WorkCoordinator.IncrementalAnalyzerProcessor.<GetOrDefaultAsync>d__33`2.MoveNext()"
@Pilchie Pilchie added Area-IDE Bug Tenet-Reliability Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner. labels May 9, 2017
@Pilchie
Copy link
Member

Pilchie commented May 10, 2017

Fixed yesterday in #19357.

@Pilchie Pilchie closed this as completed May 10, 2017
@Pilchie Pilchie added the Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented label May 10, 2017
@mattscheffer
Copy link
Contributor Author

mattscheffer commented May 10, 2017

@Pilchie Wasn't this pushed to VSUML? I just upgraded to the latest build which contains 20170509.8 and I'm still seeing the crash.

@Pilchie
Copy link
Member

Pilchie commented May 10, 2017

Should have been I think. @tmeschter ?

@Pilchie
Copy link
Member

Pilchie commented May 11, 2017

And @jasonmalinowski who I think did this insertion.

@jasonmalinowski
Copy link
Member

@mattscheffer Can you provide a dump? Dumps always make the mysterious clear.

@mattscheffer
Copy link
Contributor Author

Provided dump via email. Can send again if needed. Reopening bug as this is still crashing VS in vsuml

@mattscheffer mattscheffer reopened this May 12, 2017
@mattscheffer mattscheffer removed the Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented label May 12, 2017
@CyrusNajmabadi
Copy link
Member

Need link to the dump to investigate.

@CyrusNajmabadi
Copy link
Member

Your dump doesn't seem to match the stack trace above. The dump crashes here:

StreamJsonRpc.RemoteInvocationException: Object reference not set to an instance of an object.
   at Microsoft.CodeAnalysis.DesignerAttributes.AbstractDesignerAttributeService.<TryAnalyzeProjectInCurrentProcessAsync>d__5.MoveNext()

Which is an issue that @heejaechang is fixing here: #19466

@CyrusNajmabadi
Copy link
Member

@CyrusNajmabadi CyrusNajmabadi added the Resolution-Duplicate The described behavior is tracked in another issue label May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IDE Bug Resolution-Duplicate The described behavior is tracked in another issue Tenet-Reliability Customer telemetry indicates that the product is failing in a crash/hang/dataloss manner.
Projects
None yet
Development

No branches or pull requests

4 participants