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

Issue running WinForms Ribbon apps on .NET 5.0.7 (regression) #54335

Closed
MatthewBeardmore opened this issue Jun 17, 2021 · 5 comments · Fixed by #54244
Closed

Issue running WinForms Ribbon apps on .NET 5.0.7 (regression) #54335

MatthewBeardmore opened this issue Jun 17, 2021 · 5 comments · Fixed by #54244

Comments

@MatthewBeardmore
Copy link

MatthewBeardmore commented Jun 17, 2021

Description

Previously, running WinForms with Ribbon apps worked properly in both .NET Core 3.1 and .NET 5 5.0.6, but after updating to 5.0.7, the application crashes as soon as you attempt to choose a combobox option. I have attached a repo project based off of the sample project from https://github.com/harborsiem/WindowsRibbon/tree/master/Samples/CS/06-ComboBox. Other than the conversion from .NET Framework, it is the same as the code at that URL.

In order to reproduce, launch the project, then select any option in the comboboxes - as soon as the mouse hovers over an option, the AccessViolationException occurs.

Configuration

.NET 5.0.7
Windows 10 21H1
x64

Regression?

This previously worked in .NET 5.0.6 and .NET Core 3.1 (still works in both of these on machines that do not have 5.0.7 installed).
06-ComboBox.zip
I also have tried this against .NET 6.0 preview 4, which experiences the same issue as .NET 5.0.7.

Other information?

System.AccessViolationException
HResult=0x80004003
Message=Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Source=
StackTrace:

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jun 17, 2021
@jkotas
Copy link
Member

jkotas commented Jun 17, 2021

@MatthewBeardmore
Copy link
Author

I found issue 54132, which appears to be related. I took the SDK from #54132 (comment) and ran it against this sample project, and the sample project does not crash when selecting combo boxes.

@jkoritzinsky jkoritzinsky removed the untriaged New issue has not been triaged by the area owner label Jun 17, 2021
@AaronRobinsonMSFT
Copy link
Member

@MatthewBeardmore Thank you for reporting this issue. We already determined this behavior needed to be fixed so we are servicing .NET 5 via #54244. Reporting this helps reinforce that decision.

@elinor-fung elinor-fung added this to the 5.0.x milestone Jun 29, 2021
@jkoritzinsky
Copy link
Member

Fixed by #54244

@ghost ghost locked as resolved and limited conversation to collaborators Aug 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants