Crash after closing an Azure tab and entering something in default PowerShell tab #3111

Closed
opened 2026-01-30 23:13:16 +00:00 by claunia · 8 comments
Owner

Originally created by @hangvane on GitHub (Aug 4, 2019).

Environment

Windows build number: version 10.0.18362.239
Windows Terminal version (if applicable):0.3.2142.0 from Microsoft Store 

Steps to reproduce

  1. Fresh install of Terminal from Microsoft Store
  2. Try to open the default Azure Cloud Shell tab and close the tab without login
  3. Enter something in default PowerShell and press Enter, for example, type "abc" and press Enter

Expected behavior

Displays the return value or error information of the command

Actual behavior

Crash

Originally created by @hangvane on GitHub (Aug 4, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: version 10.0.18362.239 Windows Terminal version (if applicable):0.3.2142.0 from Microsoft Store ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Fresh install of Terminal from Microsoft Store 2. Try to open the default Azure Cloud Shell tab and close the tab without login 3. Enter something in default PowerShell and press Enter, for example, type "abc" and press Enter # Expected behavior Displays the return value or error information of the command <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> Crash
Author
Owner

@TayYuanGeng commented on GitHub (Aug 4, 2019):

Do you have a screenshot of the actual behaviour as the reported issue is too brief.

@TayYuanGeng commented on GitHub (Aug 4, 2019): Do you have a screenshot of the actual behaviour as the reported issue is too brief.
Author
Owner

@hangvane commented on GitHub (Aug 5, 2019):

Do you have a screenshot of the actual behaviour as the reported issue is too brief.
sure
1.open the terminal
1

  1. open the azure tab
    2
  2. close the azure tab
    3
  3. type "a" in default powershell tab
    4
  4. the terminal disappeared after i pressing enter without any error message
@hangvane commented on GitHub (Aug 5, 2019): > Do you have a screenshot of the actual behaviour as the reported issue is too brief. sure 1.open the terminal ![1](https://user-images.githubusercontent.com/22473909/62445028-dbf63f00-b791-11e9-9564-bf98e6d42514.jpg) 2. open the azure tab ![2](https://user-images.githubusercontent.com/22473909/62445052-ec0e1e80-b791-11e9-8bd7-6a78e9e287bb.jpg) 3. close the azure tab ![3](https://user-images.githubusercontent.com/22473909/62445139-211a7100-b792-11e9-9ec5-8eee0815d421.jpg) 4. type "a" in default powershell tab ![4](https://user-images.githubusercontent.com/22473909/62445179-3d1e1280-b792-11e9-9b90-41a2a9fc4d52.jpg) 5. the terminal disappeared after i pressing enter without any error message
Author
Owner

@zadjii-msft commented on GitHub (Aug 5, 2019):

I'm pretty sure @miniksa was investigating some other crashes that looked a lot like this.

@zadjii-msft commented on GitHub (Aug 5, 2019): I'm pretty sure @miniksa was investigating some other crashes that looked a lot like this.
Author
Owner

@miniksa commented on GitHub (Aug 5, 2019):

@hangvane, can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

image
image

Thanks!

@miniksa commented on GitHub (Aug 5, 2019): @hangvane, can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end? ![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png) Thanks!
Author
Owner

@DHowett-MSFT commented on GitHub (Aug 5, 2019):

I think i've seen this as well. I'll go digging for cabs on my machine.

@DHowett-MSFT commented on GitHub (Aug 5, 2019): I think i've seen this as well. I'll go digging for cabs on my machine.
Author
Owner

@hangvane commented on GitHub (Aug 6, 2019):

@hangvane, can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

image
image

Thanks!

https://aka.ms/AA5roiw

@hangvane commented on GitHub (Aug 6, 2019): > @hangvane, can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end? > > ![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) > ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png) > > Thanks! https://aka.ms/AA5roiw
Author
Owner

@zadjii-msft commented on GitHub (Sep 13, 2019):

This is more likely #2375 but maybe also #2525

@zadjii-msft commented on GitHub (Sep 13, 2019): This is more likely #2375 but maybe also #2525
Author
Owner

@DHowett-MSFT commented on GitHub (Nov 3, 2019):

I think both of the bugs that could have been this are now fixed. Please let me know if it still reproduces!

@DHowett-MSFT commented on GitHub (Nov 3, 2019): I think both of the bugs that could have been this are now fixed. Please let me know if it still reproduces!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3111