AccessViolationException in Binder.LookupExtensionMethodsInSingleBinder causes ServiceHub crash #62059
Comments
dotnet-issue-labeler
bot
added
Area-IDE
untriaged
DrLeh
changed the title
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
I hid all comments involved in locating the cause of the error so I can redirect this to the team that owns the code. This error was caused by a ServiceHub process crash. Specifically, this one: |
sharwell
changed the title
|
I experience the exact same behaviour quite frequently since the last VS stable update, also having the same AccessViolation as source. Happend actually always , when i have VS open for longer periods. Had similar issues before already, but in this version occuring quite more frequently. |
|
Updated to vs2022 17.2.5 yesterday, still happening. |
|
@DrLeh Can you follow the steps described here to capture a heap dump during the next crash? The heap dump can then be compressed (.zip or .7z) and attached to a report using the Report a Problem feature of Visual Studio. Thanks! |
sharwell
added
Resolution-External
|
@sharwell as i mention in the OP, the "Report a Problem" button doesn't do anything for me. Nothing is opened in my browser when I click the button. |
You can attach the files in a comment on this issue: |
|
Ok i was finally able to get the report a problem feature to work. I submitted a new ticket as it's still happening in the latest preview https://developercommunity.visualstudio.com/t/Feature-x-is-currently-unavailable-due/10189905?scope=follow I'm going to try to get some crash dumps to attach to this new ticket |
|
Reopening this since conversation is happening here along with the public ticket. |
|
In case it helps -with regard to the first error message in the above OP: this #49544 was closed because it was a duplicate of this #49005, which in turns appears to have been flagged as "resolved" by simply producing the polite error message noted above. The error was solved by telling us that we have an error and handing us a stack trace. Here's mine: StreamJsonRpc.RemoteInvocationException: Cannot enqueue data after PromiseNotToEnqueue. |
|
This is happening for me with Visual Studio Enterprise 2022 17.4.1. |
Same here (VS 2022 17.4.1). After open any ASP.Net MVC5 project, and a razor file, it always throws this in a couple of minutes. I try to repair VS2022 but no luck. I have a 17.1 community at another machine, that one has no issues at all. Update: I uninstall 17.4.1 and install 17.2.10 LTSC. It works fine for now. |
|
When fix will be released? It seems I am coding in notepad. Almost everything is failing in the text editor. |
|
That fix is around a tricky race condition. We wanted to give it a few weeks to settle in our preview builds before back porting it for servicing (wanted some real world testing to make sure there were no adverse side effects of the change). Expectation is this will be back ported next week to 17.4 and that would appear in the following servicing update. |
|
Thanks for the update @jaredpar ! Using VS.NET 2019 for now as backup. |
|
Also experiencing this issue on VS 2022 v17.4.1.
|
|
@edgariscoding Can you file a new bug on that one? That's not something I think we've seen before. |
Yep, done https://developercommunity.visualstudio.com/t/Feature-Diagnostic-analyzer-runner-is-/10214845 |
|
I am having the same issue on Visual Studio 17.4.2, see image below and stack trace:
StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. ---> System.OperationCanceledException : The operation was canceled. Only extension installed is = JetBrains ReSharper 2022.2.4 Build 222.0.20221024.165723 built on 2022-10-24 If you need any further information let me know and i am happy to share. |
|
@patdevlin That's being investigated as a part of https://developercommunity.visualstudio.com/t/Feature-x-is-currently-unavailable-due/10189905 |
|
This is happening to me with a large .sln in VS 17.9.6 (latest). StreamJsonRpc.ConnectionLostException : The JSON-RPC connection with the remote party was lost before the request could complete. ---> System.OperationCanceledException : The operation was canceled. |
|
Hi @ForteUnited, That issue is not related to the current issue. Can you file a new report so we can investigate it? Thanks! |
Shortly after starting VS2022, I start to see these several of these errors at the top, and certain intellisense features stop working .
When I click the show stack trace, I get the same error for them all:
I'm not doing anything in particular when it happens. I open a solution i've worked in for years on a previous machine, VS2022 on that machine has no issues. After coding for a bit this will happen and my intellisense drops. After restart it will work again for a few minutes.
Fully fresh install of VS 2022, no extensions added. I even ran the InstallCleanup.exe step from here https://docs.microsoft.com/en-us/visualstudio/install/uninstall-visual-studio?view=vs-2022 to do a completely fresh install.
My only other idea is that there could be some policy on my machine that is causing the JSON-RPC call to not be allowed? I'm not sure what it's connecting to though so not sure what to look for there.
After some more work on this PC, it seems like the it only happens in my older solution that has more projects, and also contains some .net standard 2.0, 2.1, and net472 web projects. I have newer solutions that are all .net 6 and don't seem to have the same issue.
I originally commented in this thread that seemed related #58102 (comment) @CyrusNajmabadi requested I create a new thread.
I have tried doing the "report a problem" button in visual studio but nothing happens when i click it.
The text was updated successfully, but these errors were encountered: