-
Notifications
You must be signed in to change notification settings - Fork 4k
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
AbstractSignatureHelpProvider crashes VS when listing overloads of generic methods #31263
Comments
Another hit here in P1: https://developercommunity.visualstudio.com/content/problem/390031/ide-crashes.html. |
@jnm2 Just hit this as well. |
@mavasani can you take a look? |
Also, this is a full VS crash, not a goldbar. Tagging @jinujoseph as well |
I have a consistent repro on 16-p1.1 by typing using System.Text.RegularExpressions;
class C
{
void M()
{
Regex.Split("", "", [||]);
}
} Sometimes it freezes when I type the final |
I hit this multiple times a day. The workaround for me is to hit Ctrl+S a lot, and when typing a |
Ah, this is better than typing in a blank line to autocomplete and then cutting and pasting. |
Investigating... |
From the stack trace it looks like the bug I fixed. |
@davidwengier @jnm2 @CyrusNajmabadi Could you guys try deploying from master and see if the issue goes away? |
Ah great. Thanks! |
When using Ctrl+Shift+Space within the argument list of a static generic method to list overloads, VS always crashes.
Repro steps:
git clone https://github.com/Microsoft/vs-streamjsonrpc.git
cd vs-streamjsonrpc
src\streamjsonrpc.sln
In VS, open the JsonRpcProxyGenerationTests.cs file.
On line 30:
this.clientRpc = JsonRpc.Attach<IServer>(this.clientStream);
Place your caret on at the start of clientStream and press Ctrl+Shift+Space to list overloads.
Crash.
This issue has been moved from https://developercommunity.visualstudio.com/content/problem/385276/abstractsignaturehelpprovider-crashes-vs-when-list.html
VSTS ticketId: 731684
These are the original issue comments:
(no comments)
These are the original issue solutions:
(no solutions)
The text was updated successfully, but these errors were encountered: