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

Visual Studio 2019 Crashing, as soon as RDP Connects #1360

Closed
vsfeedback opened this issue Jul 24, 2019 · 4 comments
Closed

Visual Studio 2019 Crashing, as soon as RDP Connects #1360

vsfeedback opened this issue Jul 24, 2019 · 4 comments
Labels
Bug Product bug (most likely) .NET Framework
Milestone

Comments

@vsfeedback
Copy link

Not sure if it only crashes when window is active or not. Also not sure if having Windows Taskbar to the right makes a difference. Using RDP full screen.

This issue has been moved from https://developercommunity.visualstudio.com/content/problem/649452/visual-studio-2019-crashing-as-soon-as-rdp-connect.html
VSTS ticketId: 948312

These are the original issue comments:

Visual Studio Feedback System on 7/18/2019, 05:47 PM (5 days ago):

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.



Visual Studio Feedback System on 7/19/2019, 08:56 AM (5 days ago):

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.



Visual Studio Feedback System on 7/19/2019, 08:56 AM (5 days ago):

This feedback is being re-triaged as we are moving it to another team that can better help with the issue. Thanks for your patience.

These are the original issue solutions:
(no solutions)

@weltkante
Copy link

I assume there's a private stacktrace attached to the vsfeedback which points to WPF being responsible for the VS crash? Otherwise it makes no sense that this ends up in the WPF repo ...

@rladuca
Copy link
Member

rladuca commented Jul 24, 2019

Internally this was called out as related to #1198 .

@vatsan-madhavan I wasn't able to find the associated stacks and dumps on the internal tickets, so I don't feel comfortable duping this immediately. We can talk in triage.

@vatsan-madhavan
Copy link
Member

In the internal ticket history, I can see that @jekelly made the association between this and #1198.

@grubioe grubioe added area-netfx Bug Product bug (most likely) labels Jul 26, 2019
@grubioe grubioe added this to the Future milestone Jul 26, 2019
@SamBent
Copy link
Contributor

SamBent commented Jun 11, 2020

The private information was removed from the vsfeedback ticket by the time the issue arrived here; no one knows why or how. Without that, there's nothing we can do - I'm closing the issue.

If it really is a dupe of #1198, a fix was shipped in servicing updates to .NET 4.8 last September.

@SamBent SamBent closed this as completed Jun 11, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Apr 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Product bug (most likely) .NET Framework
Projects
None yet
Development

No branches or pull requests

7 participants