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

Crash when navigating the navigation menu after selecting a DevBox. #2948

Open
dhoehna opened this issue May 16, 2024 · 4 comments
Open

Crash when navigating the navigation menu after selecting a DevBox. #2948

dhoehna opened this issue May 16, 2024 · 4 comments
Labels
Area-Core Related to Dev Home as a whole Issue-Bug Something isn't working or needs investigation Priority-2 Severity-Crash Bug that is causing a crash

Comments

@dhoehna
Copy link
Contributor

dhoehna commented May 16, 2024

Dev Home version

Canary

Windows build number

No response

Other software

No response

Steps to reproduce the bug

  1. Click on Machine Configuration
  2. Click "Create your new environment"
  3. Select an environment
  4. Click Next
  5. Wait for the adaptive card to load.
  6. with the keyboard navigate to the "Previous" button
  7. Click enter.
  8. Press tab until focus is on "Introducing DevHome"
  9. Press tab again. Crash.

Expected result

The application does not crash.

Actual result

DevHome crashes. In Debug, the error is "No Such Interface Supported" no other information.

In normal operation, tabbing after "Introducing Dev Home" will go to the next tab in the cycle.

I ran the app under Windbgx. The stack was mainly winui 3. This might be a winui3 issue.

Included System Information

No response

Included Extensions Information

No response

@dhoehna dhoehna added the Issue-Bug Something isn't working or needs investigation label May 16, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage New issue that the core contributors need to triage label May 16, 2024
@dhoehna dhoehna added the Severity-Crash Bug that is causing a crash label May 16, 2024
@dhoehna
Copy link
Contributor Author

dhoehna commented May 16, 2024

I would attach the logs, but it does not have any information about the crash.

@dhoehna
Copy link
Contributor Author

dhoehna commented May 16, 2024

Repros with only 1 extension installed. I tried with both the Hyper-V extension, and Azure Extension.

@dhoehna
Copy link
Contributor Author

dhoehna commented May 16, 2024

Found another crash.

  1. Click on Machine Configuration
  2. Click on "Set up an environment"
  3. Select the environment
  4. Click Next
  5. with the keyboard navigate to the "Previous" button
  6. Press Enter
  7. Tab until the Environment box is selected.
  8. Press tab one more time.

@krschau krschau added the Area-Core Related to Dev Home as a whole label May 20, 2024
@krschau
Copy link
Contributor

krschau commented May 22, 2024

Labeling Priority-2, since while this is a crash (bad) the repro steps as we can tell so far are not a common path.

@krschau krschau added Priority-2 and removed Needs-Triage New issue that the core contributors need to triage labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Core Related to Dev Home as a whole Issue-Bug Something isn't working or needs investigation Priority-2 Severity-Crash Bug that is causing a crash
Projects
None yet
Development

No branches or pull requests

2 participants