terminal: Opening/Closing tabs causes exit / blocked UI thread

NOTE: This is different from, but may be related to, #2230

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version: 0.3.2142.0

Steps to reproduce

  1. Open a new Windows Terminal instance
  2. Open a second tab using either the “+” button
  3. Close the new tab using CTRL+W, middle clicking the tab, or clicking the tab’s “x”

Repeat steps 2-3 as fast as possible.

Expected behavior

Tabs continue to open and close.

Actual behavior

PowerShell - Most of the time, WT stops responding and interacting with it shows the “WindowsTerminal.exe is not responding” modal

CMD / WSL - WT stops responding for about 1 second and then exits (also happens for PowerShell sometimes)

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 1
  • Comments: 15 (11 by maintainers)

Commits related to this issue

Most upvoted comments

@utybo yep, hence why the issue is still open. We’ll close the issue once a fix has been found and a PR with that fix has been merged 😜

I’m getting the same issues without middle-click - for me it it becomes unresponsive when I open WindowsTerminal and click the dropdown menu to open a Command Prompt-style tab, then close the Powershell tab fairly quickly.

Yea this is pretty trivially repro-able. I got it with a quick click on the new tab followed by immediately middle clicking. Thanks for the report!