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

Form is not responding after clicking on Button then close Form #6794

Closed
Lydia-Shi opened this issue Mar 4, 2022 · 9 comments
Closed

Form is not responding after clicking on Button then close Form #6794

Lydia-Shi opened this issue Mar 4, 2022 · 9 comments
Labels
tracking-external-issue An issue is caused by an external system and won't be fixed in this repo

Comments

@Lydia-Shi
Copy link
Member

  • .NET Core Version:
    .NET 7.0.100-preview.3.22153.22

  • Have you experienced this same bug with .NET Framework?:
    No

Problem description:
Form is not responding after clicking on button then close Form.
Button_NotRespond

Expected behavior:
Form and VS all work well.

Minimal repro:

  1. Create a Winforms .NET Core application
  2. Drag and drop a Button control into Form designer
  3. Build and run
  4. Click on button, then try to close Form

More info:

  1. This is a regression issue, and cannot repro in 7.0.100-preview.3.22152.16
  2. This issue affects many controls: TextBox, Button, Label, PropertyGrid, DataGridView, and …
@Lydia-Shi Lydia-Shi added the 💥 regression-preview Regression from a preview release label Mar 4, 2022
@willibrandon
Copy link
Contributor

willibrandon commented Mar 5, 2022

@Lydia-Shi - When your application becomes unresponsive, what happens if you then click Stop Debugging in VS?

I might be seeing the same or a similar issue in my environment. If I try to stop debugging once the application becomes unresponsive, I get the Stop Debugging In Progress dialog popup and I must click the Stop Now button to force stop the debugging session.

@Lydia-Shi
Copy link
Member Author

@willibrandon After stopping debugging in VS, the following window is displayed.
image

@willibrandon
Copy link
Contributor

Then I'm fairly certain I'm running into the same issue as you.

StopDebuggingInProgress

If I can be of any assistance troubleshooting this, please let me know.

@dreddy-work
Copy link
Member

@tommcdon is investigating this issue. Will update the thread as soon as we have a solution.

@WPMGPRoSToTeMa
Copy link
Contributor

Note that I already reported this bug in dotnet/runtime#65664.

@tommcdon
Copy link
Member

tommcdon commented Mar 8, 2022

@Lydia-Shi would you mind trying to disable Intellitrace in Visual Studio to see if it works around the issue? I believe that this issue is actually a Visual Studio problem and is tracked on Devdiv internal bug #'s 1495188 and 1495179.

@RussKie RussKie added tracking-external-issue An issue is caused by an external system and won't be fixed in this repo and removed 💥 regression-preview Regression from a preview release labels Mar 8, 2022
@RussKie
Copy link
Member

RussKie commented Mar 8, 2022

Closing as duplicate of dotnet/runtime#65664.

@RussKie RussKie closed this as completed Mar 8, 2022
@Lydia-Shi
Copy link
Member Author

@Lydia-Shi would you mind trying to disable Intellitrace in Visual Studio to see if it works around the issue? I believe that this issue is actually a Visual Studio problem and is tracked on Devdiv internal bug #'s 1495188 and 1495179.

@tommcdon Yes, it's a workaround, after disabling Intellitrace, this issue will not occur.

@Cassie-Li01
Copy link

Verified on .NET 7.0.100-preview.4.22201.8, it is fixed. Please see the git as below:
fixed

@ghost ghost locked as resolved and limited conversation to collaborators May 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tracking-external-issue An issue is caused by an external system and won't be fixed in this repo
Projects
None yet
Development

No branches or pull requests

7 participants